Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple silicon Mac chips
- Thread starter Aquamite
- Start date
- Sort by reaction score
iMHO, it’s the technical threads that add value to this forum far more than the rumour / opinion threads (and yes, that itself is an opinion).
People search through the older technical threads all the time on this forum. I doubt that happens with the „front page” threads.
Don’t knock things that add value.
Ah unfortunately cpu-monkey is a little unreliable. This is not the first time I've found them making mistakes. The M2 and M3 TFLOPS are right, but the M4 and M5 are wrong. I can't confirm their clock speed for the M5. But even if it is right, the TFLOPS they calculated from it is still wrong.I've edited the TFLOPS for M2, M3 and M4 according to these sources, M5 already matched the source:
Apple M2 (10 Core) Benchmarks & Specs
Apple M2 (10 Core) - 3DMark Time Spy and FP32 benchmarks and specifications for this integrated graphicswww.cpu-monkey.com
Apple M3 (10 Core) Benchmarks & Specs
Apple M3 (10 Core) - 3DMark Time Spy and FP32 benchmarks and specifications for this integrated graphicsApple M4 (10 Core) Benchmarks & Specs
Apple M4 (10 Core) - 3DMark Time Spy and FP32 benchmarks and specifications for this integrated graphics
M5: https://www.cpu-monkey.com/en/igpu-apple_m5_10_core
M4: 1280*1.58*2/1000 = 4.0448 TFLOPS
M5: 1280*1.9*2/1000 = 4.864 TFLOPS (again, that's if they have the new GPU clock speed right)
Another problem is that cpu-monkey lists double throughput of FP16 relative to FP32 for all of these chips, but Apple didn't gain the ability to do that until the M5. And finally, pretty sure the number of execution units is 4 per core, so it should be 40 units not 160 units*. Apple has a SIMD width of 32 for a total of 40*32 = 1,280 FP32 units (which cpu-monkey does get right, though we don't know yet about the M5 structure and how Apple doubled FP16 throughput, but CPU-monkey doesn't list that anyway). Hopefully I haven't led you astray, but if so @name99 or @leman can correct me.
*EDIT: so tired I managed to confuse myself. It should be right now. I think where CPU monkey got confused and momentarily confused me, is that Apple used to allow 16*32 = 512 threads per core (I believe since Apple has bumped that up to 32*32 = 1024 threads per core, but that's not the same as the execution units/core counts).
Metal compute shaders threadgroup & threadExecutionWidth
Can someone explain in simple terms what threadgroup conceptually is in Metal compute shaders and other terms such as SIMD group, threadExecutionWidth (wavefront)? I read the docs but am more confu...
Last edited:
@Basic75
No Mac before the introduction of Apple Silicon had a ProRes decoder/encoder except the Afterburner card in the 2019 Mac Pro.
The T2 chip was restricted to H.264/265, to add that acceleration to the iMac Pro as the Xeon CPU didn't have Intel's QuickSync.
My impression was that Apple built T2 functionality into Apple Silicon Gen1, so to add ProRes hardware decode seems an oddity, since they had hitherto optimised MacOS to handle ProRes using the CPU/GPU.
During the year that it took to develop the M1Pro/Max SoCs, they presumably ported the Afterburner FGPA hardware design into Apple Silicon's Media Engine, and introduced ProRes acceleration.
So it seems very unlikely that there is any acceleration of ProRes decode in the M1, beyond the H.26* acceleration imported from the T2 chip.
No Mac before the introduction of Apple Silicon had a ProRes decoder/encoder except the Afterburner card in the 2019 Mac Pro.
The T2 chip was restricted to H.264/265, to add that acceleration to the iMac Pro as the Xeon CPU didn't have Intel's QuickSync.
My impression was that Apple built T2 functionality into Apple Silicon Gen1, so to add ProRes hardware decode seems an oddity, since they had hitherto optimised MacOS to handle ProRes using the CPU/GPU.
During the year that it took to develop the M1Pro/Max SoCs, they presumably ported the Afterburner FGPA hardware design into Apple Silicon's Media Engine, and introduced ProRes acceleration.
So it seems very unlikely that there is any acceleration of ProRes decode in the M1, beyond the H.26* acceleration imported from the T2 chip.
Last edited:
This is nice.
FWIW a little label or note about this in your post would have spared folks the confusion about why you're posting all this
A little digging shows that https://www.apple.com/final-cut-pro/docs/Apple_ProRes.pdf only mentions the M1 Pro, Max and Ultra.
I THINK (patents and some benchmarks I've seen both suggest this) that M5 FP16 throughput is 3x FP32 -- but ONLY for matrix multiply.Ah unfortunately cpu-monkey is a little unreliable. This is not the first time I've found them making mistakes. The M2 and M3 TFLOPS are right, but the M4 and M5 are wrong. I can't confirm their clock speed for the M5. But even if it is right, the TFLOPS they calculated from it is still wrong.
M4: 1280*1.58*2/1000 = 4.0448 TFLOPS
M5: 1280*1.9*2/1000 = 4.864 TFLOPS (again, that's if they have the new GPU clock speed right)
Another problem is that cpu-monkey lists double throughput of FP16 relative to FP32 for all of these chips, but Apple didn't gain the ability to do that until the M5. And finally, pretty sure the number of execution units is 4 per core, so it should be 40 units not 160 units*. Apple has a SIMD width of 32 for a total of 40*32 = 1,280 FP32 units (which cpu-monkey does get right, though we don't know yet about the M5 structure and how Apple doubled FP16 throughput, but CPU-monkey doesn't list that anyway). Hopefully I haven't led you astray, but if so @name99 or @leman can correct me.
*EDIT: so tired I managed to confuse myself. It should be right now. I think where CPU monkey got confused and momentarily confused me, is that Apple used to allow 16*32 = 512 threads per core (I believe since Apple has bumped that up to 32*32 = 1024 threads per core, but that's not the same as the execution units/core counts).
Metal compute shaders threadgroup & threadExecutionWidth
Can someone explain in simple terms what threadgroup conceptually is in Metal compute shaders and other terms such as SIMD group, threadExecutionWidth (wavefront)? I read the docs but am more confu...stackoverflow.com
Do you remember that "I know more about American Girl than you do, genius!" Vine? That's the vibe here.