News for hackers. Stuff that matters.

A comment on Apple M1 support for TensorFlow 2.5 pluggable device API. Parent comment

Re:Apple M1 support for TensorFlow 2.5 pluggable device API by codelord on Tuesday June 08, 2021 @10:12PM (#27443480)
It's not really fair to compare a discrete GPU to a mobile GPU, I only provided this as a comparison for someone who maybe has one of these at home. And btw, you are talking about TF32 performance not FP32. TF32 actually uses 16 bits. A100's FP32 performance is actually lower than 3090, it's 19.5 TFLOPS: https://www.nvidia.com/content/dam/en-zz/Solutions/Data-Cent...

FP16 performance is also relevant as a lot of people now train in FP16. The default for pytorch/TF is still FP32.

[ Parent | on HN ]
Re:Apple M1 support for TensorFlow 2.5 pluggable device API by rubatuga on Wednesday June 09, 2021 @12:00AM (#27444085)
TF32 is 19 bits! Default for pytorch and TF is TF32!
[ Parent | on HN ]
Re:Apple M1 support for TensorFlow 2.5 pluggable device API by codelord on Wednesday June 09, 2021 @12:51PM (#27450182)
Oops. You are right.
[ Parent | on HN ]
Re:Apple M1 support for TensorFlow 2.5 pluggable device API by 6gvONxR4sf7o on Tuesday June 08, 2021 @10:24PM (#27443553)
I’ve been mostly using TPUs lately and non-TF32 GPUs at work, so I don’t have any practical experience with TF32, but the sales pitch seems pretty good. Do you have any personal experience on whether it’s as much of a drop in replacement for fp32 as they suggest?
[ Parent | on HN ]
Re:Apple M1 support for TensorFlow 2.5 pluggable device API by codelord on Tuesday June 08, 2021 @10:30PM (#27443591)
I haven't used TF32 personally, but I think the sales pitch is not too far off. Most of the time I use mixed-precision training which should be similar to FP16/TF32 in terms of performance. It does tremendously speed up training.
[ Parent | on HN ]