5 ms·
That's great if you App is compute bound. "May all your Processes be compute bound." Back in the real world most of the time your Process will be io bound. I th
by ben_bai 6y ago
That's great if you App is compute bound. "May all your Processes be compute bound." Back in the real world most of the time your Process will be io bound. I think that's the real innovation of the M1 chip.
- isitdopamine 6y agoExplain please. What does the M1 do to IO loads?
- 1_player 6y agoNothing. Compute speed isn't that important if you're waiting on IO is GP's point.
- K0balt 6y agoOn die memory and storage. No bottlenecks, very little latency.
- matthewmacleod 6y agoImportant to clarify this every time it comes up: there is no on-die memory on the M1. It is normal, everyday, DDR4 memory which is located near to the processor. It's actually quite high latency at ~100ns.
- unicornfinder 6y agoIndeed and I was quite surprised by this as it's actually higher latency than you'd get on AMD or Intel's chips.
- gpderetta 6y agoExactly because of the "real world" argument, turns out that a lot of actual real world loads are CPU bounds because they are so wastefully implemented. IO of all kinds has extremely high bandwidth these days and OoO helps hide the latency.
- Ar-Curunir 6y ago128-bit muls really help speed up finite field impl, which speed up elliptic curve crypto. That’s one crucial place where faster code helps.