Re:Deep learning has a size problem
by RocketSyntax on Saturday November 09, 2019 @06:05PM
(#21495114)
Deep learning doesn't parallelize well. Would be cool if you could loan CPU cycles on your phone or home computers while at work.
[ Parent
| on HN ]
Actually it parallelizes extremely well, so that large companies are able to create monster models like mentioned in the article in the first place by just throwing money at the problem with TPUs and similar highly parallelized accelerators. It just doesn't lend itself well to distributed computing due to e.g. throughput requirements.
Re:Deep learning has a size problem
by RocketSyntax on Sunday November 10, 2019 @09:16AM
(#21498021)
That's just vertical scale. Distributed is what I was referring to. See comment below.
Re:Deep learning has a size problem
by question_away on Saturday November 09, 2019 @06:25PM
(#21495240)
In what way does it not parallelize well? There are mounds of research in federated learning.
Re:Deep learning has a size problem
by kyle_grove on Saturday November 09, 2019 @07:25PM
(#21495531)
In fact, one of the chief advantages of the BERT/Transformer architecture over ELMO/LSTM is the ability to parallelize.
Re:Deep learning has a size problem
by RocketSyntax on Saturday November 09, 2019 @08:48PM
(#21495881)
I've read that you can't split up large layers to be trained on separate processors either horizontally (one layer per processor) or vertically (parts of many layers).
On a shared memory system there's little need to do that - there's much more parallelism to be had from accelerating fine grained operations, like matrix multiplications to compute each layer's output.
On a distributed system, splitting up layers between machines to do distributed training is pretty much what Google initially designed Tensorflow for. Generally it scales less well due to the need to communicate massive amounts of data between nodes and much lower network throughput than what GPU/TPU memory provides.