Amazon Tensor Flow vs. Caffe2 vs. Pytorch

A well-suited scenario for using AWS Tensor Flow is when having a project with a geographically dispersed team, a client overseas and large data to use for training. AWS Tensor Flow is less appropriate when working for clients in regions where it hasn't been allowed yet for use. Since smaller clients are in regions where AWS Tensor Flow hasn't been allowed for use, and those clients traditionally don't have enough hardware, this situation deters a wider use of the tool.

Incentivized

They have created Pytorch Lightening on top of Pytorch to make the life of Data Scientists easy so that they can use complex models they need with just a few lines of code, so it's becoming popular. As compared to TensorFlow(Keras), where we can create custom neural networks by just adding layers, it's slightly complicated in Pytorch.

Incentivized

• Amazon Elastic Compute Cloud (EC2) allows resizable compute capacity in the cloud, providing the necessary elasticity to provide services for both, small and medium-sized businesses.
• Tensor Flow allows us to train our models much faster than in our on-premise equipment.
• Most of the pre-trained models are easy to adapt to our clients' needs.

Incentivized

• flexibility
• Clean code, close to the algorithm.
• Fast
• Handles GPUs, multiple GPUs on a single machine, CPUs, and Mac.
• Versatile, can work efficiently on text/audio/image/tabular datasets.

Incentivized

• SageMaker isn't available in all regions. This is complicated for some clients overseas.
• For larger instances, when using a GPU, it takes a while to talk to a customer service representative to ask for a limit increase. Given this, it's recommendable to ask in advance for a limit increase in more expensive and larger cases; otherwise, SageMaker will set the limit to zero by default.
• Since the data has to be stored in S3 and copied to training, it doesn't allow to test and debug locally. Therefore, we have to wait a lot to check everything after every trail.

Incentivized

• Since pythonic if developing an app with pytorch as backend the response can be substantially slow and support is less compares to Tensorflow

Incentivized

The big advantage of PyTorch is how close it is to the algorithm. Oftentimes, it is easier to read Pytorch code than a given paper directly. I particularly like the object-oriented approach in model definition; it makes things very clean and easy to teach to software engineers.

Incentivized

Microsoft Azure is better than Amazon Tensor Flow because it provides easier and pre-built capabilities such as Anomaly Detection, Recommendation, and Ranking. AWS is better than IBM Watson ML Studio because it has direct and prebuilt clustering capabilities AWS, like IBM Watson ML Studio, has powerful built-in algorithms, providing a stronger platform when comparing it with MS Azure ML Services and Google ML Engine.

Incentivized

Pytorch is very, very simple compared to TensorFlow. Simple to install, less dependency issues, and very small learning curve. TensorFlow is very much optimised for robust deployment but very complicated to train simple models and play around with the loss functions. It needs a lot of juggling around with the documentation. The research community also prefers PyTorch, so it becomes easy to find solutions to most of the problems. Keras is very simple and good for learning ML / DL. But when going deep into research or building some product that requires a lot of tweaks and experimentation, Keras is not suitable for that. May be good for proving some hypotheses but not good for rigorous experimentation with complex models.

Incentivized

• Positive: It has allowed us to work with our overseas teams without any large hardware investing.
• Positive: Pre-trained models significantly reduce the time to develop solutions for our clients.
• Negative: Since it's a relatively new tool, you have to be careful about not paying for large errors while learning to use the tool.

Incentivized

• The ability to make models as never before
• Being able to control the bias of models was not done before the arrival of Pytorch in our company

Incentivized