This page has the first mention of Google TPUs since the initial announcement from Google.
Anyone know what the status is? When TPUs will be allowed to be used in Google Cloud?
I'm confused as to why they ever announced it at a big event like Google I/O rather than a paper or even a simple blog post if they aren't going to give people access to them. There's some hint of it being offered in conjunction with TF and other ML cloud offerings in the blog post[1], and this 'XLA compiler framework' looks it's related. But I'm still wondering how much time people have to wait.
> When TPUs will be allowed to be used in Google Cloud?
TPUs are only useful for prediction, not training, and for very high volumes of work where energy use is a major cost, so, it's for Google and FaceBook-type of situations. They are not designed as accelerated general purpose processors for deep learning.
Cheap inference can be done on CPUs as well, because production models can be optimized to only a small fraction of the computation (20x reductions are not impossible) by pruning neurons, weight quantization and other techniques.
The aforementioned google translate paper suggests so.
My hunch is that TPUs work with a mix of 8 bit and 16 bit integer arithmetic on quantized networks with quantized data [1].
As far as I know nobody has managed to make SGD work properly with integer weights and that could be a reason why TPUs are not used for training (yet).
Probably memory. Unless their ASICs have some kind of ultra fast on-chip memory. That's why GPUs still reign supreme. FPGAs have started seeing use for inference for those of us without the billion dollar budgets needed to develop ASICs.
Neato! I'm surprised they went with a JIT compiler over a full-on compiler, but that might just be me not understanding:
a) Compilers
b) How a JIT compiler would apply to this situation
My lab-mate Jan Gosmann recently did something similar for our spiking neural network software Nengo [1]. Although it isn't Deep Learning, it also builds a computational graph of operations. He ended up optimising the layout of the operations in memory to increase the efficiency of Numpy operations and reduce the amount of time spent in Python. He's in the process of writing a paper about it.
JITs can take into account the actual data being processed. And most importantly here, its size.
Knowing the size will help with making chunks of work fit into L1, L2, L3 caches. Creating sensible SIMDs operations. Choosing what goes into a warp.
Also, sometimes it is better to rematerialize a computation than having stored it; and the threshold to do it depends on the space and computing costs.
Languages like Halide [1] let you hand-tune this threshold. I guess this is the kind of work XLA does here.
Precisely. Just-in-time compilation allows the compiler to specialize the generated code for the shapes of the Tensors that appear at run time. This allows us to generate better code.
XLA also has an experimental ahead-of-time mode, which we think will be particularly interesting for some production and mobile deployments. This is all work in progress though, and we're looking forward to getting the community involved.
The corresponding documentation hasn't been pushed yet; I'll post a link when it is up.
Note that XLA is work in progress --- we're releasing the code early because we want to get the community involved. The GPU backend is in good shape, and improving by the day. We haven't had as much time to devote to the CPU backend, and it only has limited support for parallelism. Contributions welcome!
Anyone know what the status is? When TPUs will be allowed to be used in Google Cloud?
I'm confused as to why they ever announced it at a big event like Google I/O rather than a paper or even a simple blog post if they aren't going to give people access to them. There's some hint of it being offered in conjunction with TF and other ML cloud offerings in the blog post[1], and this 'XLA compiler framework' looks it's related. But I'm still wondering how much time people have to wait.
[1]:https://cloudplatform.googleblog.com/2016/05/Google-supercha...