3 ms·

Two problems. 1) Tensorflow sucks 2) People that are actually experts in deep learning prefer Pytorch or Caffe2 so your mindshare thing is wrong, once the dust

Two problems. 1) Tensorflow sucks 2) People that are actually experts in deep learning prefer Pytorch or Caffe2 so your mindshare thing is wrong, once the dust of the Tensorflow hype train clears people will choose tools that are actually any good

dsacco 9y ago
Why do you believe "Tensorflow sucks", and why do you believe PyTorch or Caffe2 is better, and for what metrics?
- ActsJuvenile 9y ago
  Two metrics stood out in my experiments with CNNs back in May 2017: 1) Compilation speed for a jumbo CNN architecture: Tensorflow took 13+ minutes to start training every time network architecture was modified, while PyTorch started training in just over 1 minute. PyT suits my style of interactive coding far better. 2) Memory footprint: I was able to fit 30% larger batch size for PyTorch over Tensorflow on Titan X cards. Exact same CNN architecture. Both frameworks had major releases since May, so I am sure these metrics might have changed by now. However I ended up adopting PyT for my project.
  - chronic732 9y ago
    This post is spot on. Google is actually very scared of PyTorch since nearly all new AI research papers are using PyTorch. This means in 1-2 years or so, most companies will be using PyTorch for training and Caffe for deployment. Tensorflow doesn't even have an implementation of the latest ImageNet winner, DenseNet, but PyTorch does! I have sources on the Tensorflow team saying they are scrambling to make another higher level wrapper for tensorflow at the level of PyTorch.
  - jamesblonde 9y ago
    Jumbo CNNs are not the battleground. The real battleground is distribution. The first framework that scales out without placing much onus on the programmer will win, IMO. Facebook already showed that Caffe2 scales to 256 GPUs for imagenet. Tensorflow need to show it can scale as well. PyTorch needs to work on usability - model serving, integration in ecosystems like Hadoop, etc.

dsacco 9y ago

Why do you believe "Tensorflow sucks", and why do you believe PyTorch or Caffe2 is better, and for what metrics?

ActsJuvenile 9y ago
Two metrics stood out in my experiments with CNNs back in May 2017: 1) Compilation speed for a jumbo CNN architecture: Tensorflow took 13+ minutes to start training every time network architecture was modified, while PyTorch started training in just over 1 minute. PyT suits my style of interactive coding far better. 2) Memory footprint: I was able to fit 30% larger batch size for PyTorch over Tensorflow on Titan X cards. Exact same CNN architecture. Both frameworks had major releases since May, so I am sure these metrics might have changed by now. However I ended up adopting PyT for my project.
- chronic732 9y ago
  This post is spot on. Google is actually very scared of PyTorch since nearly all new AI research papers are using PyTorch. This means in 1-2 years or so, most companies will be using PyTorch for training and Caffe for deployment. Tensorflow doesn't even have an implementation of the latest ImageNet winner, DenseNet, but PyTorch does! I have sources on the Tensorflow team saying they are scrambling to make another higher level wrapper for tensorflow at the level of PyTorch.
- jamesblonde 9y ago
  Jumbo CNNs are not the battleground. The real battleground is distribution. The first framework that scales out without placing much onus on the programmer will win, IMO. Facebook already showed that Caffe2 scales to 256 GPUs for imagenet. Tensorflow need to show it can scale as well. PyTorch needs to work on usability - model serving, integration in ecosystems like Hadoop, etc.