Re:Google TPU Performance Analysis
by Dylan16807 on Friday August 25, 2017 @10:35AM
(#15098731)
> They aren't inferior but you can't just multiply by 4 here either.
Yeah but there wasn't a suggestion to do so. Just by raw count there are issues with 25x.
> NVidia's GPUs do not have broken designs.
The part where the current generation sticks in a single FP16x2 unit per 128 FP32 units, so that if your code triggers them it runs 64x slower on FP16 while leaving all the FP32 units idle? That's broken as far as I can see, there to upsell you the pro cards.
Anything that would make 8 bit math slower than 32 bit math is just a fundamental lack of forethought. It's not preferred by GPU design, and shouldn't be used as a point against GPUs in general.
But the actually important part here is that the register and bypass networks to pass 4 bits of int8 data around are way more complicated than those required to pass a single float32 around and that's where Google's decision to restrict the flexibility of its TPU pays big dividends. NVidia's GPUs do not have broken designs. They're just making compromises based on the need to handle a wider variety of use cases.