[ben_bai]

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.

[gpderetta]

Exactly 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.

[isitdopamine]

Explain please. What does the M1 do to IO loads?

[1_player]

Nothing. Compute speed isn't that important if you're waiting on IO is GP's point.

[boomlinde]

In that case it's a confusing point, given GGP calls this nothingness "the real innovation of the M1". GP is asking what the innovation is.

[harperlee]

It’s clearer if for M1 you read “the new architecture promoted by Apple around their M1 processor”.

[kllrnohj]

What new architecture? Other than the addition of a neural unit, it's an identical architecture to every other APU from the last decade?

[boomlinde]

It would be more clear if someone answered the question.

[K0balt]

On die memory and storage. No bottlenecks, very little latency.

[matthewmacleod]

Important 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]

Indeed and I was quite surprised by this as it's actually higher latency than you'd get on AMD or Intel's chips.

[Ar-Curunir]

128-bit muls really help speed up finite field impl, which speed up elliptic curve crypto. That’s one crucial place where faster code helps.