Colab Pro
11–20 of 108 posts
Re: Colab Pro
#12Re: Colab Pro
#13Earlier quoted context omitted.
We should really thank Mathematica for the notebook format.
Did mathematica invent the notebook format? Just curious..
Re: Colab Pro
#14A preemptible P100 + VM on Google Compute Engine is about ~$0.45/hr, so to exceed that value with Colaboratory Pro (ignoring conveience factors) you'd need to train for more than 22 hours in a month. Which, for deep learning, is not too unreasonable. Reading between the lines of both the signup page and up-to-date FAQ, it seems like the free TPU in Colab notebooks will be depreciated, which isn't too surprising.
To clarify, does that mean you can continuously train a model for e.g. hundred of hours or are you still limited by the 24 hours notebook limit?
Re: Colab Pro
#15Re: Colab Pro
#16Good idea, but it's the first premium product that I've seen where the pitch is 'you may get certain features if you subscribe'. In another words there is no guarantee and a premium subscriber may still end up with same GPU as a free user. You may end up with a high-end V100 (not available to free) might be a better pitch.
However, they could at least define expected and minimum capacity. They might omit it because the business in this – aside from capturing users in their ecosystem – is arbitraging wholesale GPU price against consumer monthly needs, along with scaling the free tier.
[1] "Why aren't resources guaranteed in Colab Pro?" on https://colab.research.google.com/signup
Re: Colab Pro
#17Colab is the best notebook I've ever used. It is a real game-changer and I can totally understand why people who use daily would pay for it.
We should really thank Mathematica for the notebook format.
I can tell you definitively that Sage Notebook is very Mathematica inspired. The IPython console looked a lot like Mathematica, mainly because Fernando Perez (who was a physicist) had used Mathematica a lot and wanted something similar but (much) better. In 2005 there was a project to make an IPython notebook interface as an OS X graphical application, which got demoed at Sage Day 1 (in Feb 2006). That motivated me to get interested in doing something similar, but using Javascript and HTML instead. I hired Alex Clemesha, who just finished his physics undergrad and was a heavy Mathematica user to work on Sage fulltime. He did a lot of work with me during 2006 to create a web-based notebook interface (and also to provide a mathematica-like graphics compatibility layer for Python, which is in Sage). The Sage notebook felt pretty similar in 2007 to what Jupyter notebook feels like, and it definitely inspired the UI. We developed Sage notebook heavily and then all sort of lost interest and moved on to other things (e.g., Jason Grout, who was involved a lot with the Sage notebook went to work at Bloomberg, where he did a massive amount of work on JupyterLab). Fortunately, Fernando Perez and others got incredible grant support and many fantastic engineers together built the Jupyter notebook. Jupyter notebook provided the same sort of cell/output UI as we had with the Sage notebook, but was much more general purpose (many kernels) and used more "modern" implementation techniques, by 2011 standards at least.
There's a lot of amazing things about the Mathematica notebook that we never even tried to implement. For example, Mathematica has a much more sophisticated nested structure. Also, by default Mathematica shares one kernel across multiple notebooks (or at least it did last time I tried it).
Just to finish the story, in 2013 I started CoCalc to make a fully realtime collaborative notebook interface. Around the same time, many other people started another project called JupyterLab that reimplemented a Jupyter notebook client using much more powerful modern approaches. In addition, there's a lot more going on regarding notebook clients these days, including Nteract, Kaggle kernels, and http://deepnote.com/. Some people like me who work on these surely played around a lot with Mathematica notebooks when they were kids :-).
Re: Colab Pro
#18Re: Colab Pro
#19It's a great tool and it lets you focus on the code and the models, instead of the hardware and OS. But $9.99/month is a little expensive for my taste.
You can't customize it and if they change something you have to install software by hand sometimes. It should be $1.99/month, that's the kind of price I'd pay for this basic cloud computing service.
edit: I use Colab to play with ML models. I really don't think it's possible, for instance, to train a model on Imagenet using Colab. So Colab is similar to the microwave, if you want to cook a serious recipe you should use a real kitchen.
Re: Colab Pro
#20It’s hard for me to understand why Colab would build such a vague pro tier instead of the simplest possible solution: let me pay for my compute.
There’s so much more potential, too; they could offer whole clusters on demand, with really simple Python integrations say using dask, or ray.