2 ms·
I think a lot of the critique here is misguided. The summary at the end seemed to me entirely reasonable: writing good code for parallelism is very hard, and mo
by ggm 5y ago
I think a lot of the critique here is misguided. The summary at the end seemed to me entirely reasonable: writing good code for parallelism is very hard, and moves the cost upward into software which has to be really well written to work. Boosting IO and cache will help with some things, but absent clockspeed, making an M2 significantly better than an M1 is hard.
I don't see why people complain its only one benchmark. to import 100MB of image data invites all of the IO, Cache and CPU to play along because this is encoded data: it has to be mapped out of one form, transformed into another, as a stream of data and its a lot bigger than either a single fetch from memory, or a single bus transaction. Its ameneble to parallelism within some limits depending on the nature of the encoding. It's also a real-world test.