Umm, running a 1990s fortran code that's a CFD simulation is a "real" workload. Seems relatively likely that any floating point heavy code would act similarly. Hard to say if it's the matrix multiple or the memory bandwidth that's giving apple such a large lead.
Normally I'd discount using a 28 core Intel CPU from 2019, but from what I can tell Intel hasn't improved much since then. Keep in mind that Intel has a specialized vector unit (AVX256 or AVX512 depending on the model), and the listed CPU is pretty high end (with 6 memory channels) where the normal i5/i7/i9 is only 2.
So sure it's not a video compression, gaming, or web browing benchmark, but some folks do run floating point heavy codes. Unlike CUDA, which requires a rewrite, this code wasn't specifically optimized for the M1.
Hey man, maybe I'm a bot too. Who knows. Blip bloop. But these are just computer chips and fresh low karma accounts with vitriol dialed to the max is a-typical of HN. By all means, M1 is the worst, why froth at the mouth about it in this manner? You explain it.
I don't have to explain anything, HN is based on the ideals of arguing in good faith and not vilifying people for their opinions. If you think they're being harsh, then say that. If you think they're wrong, then refute them. But if you're solely seeking to bash them, why even comment in the first place? How does that advance anyone's understanding of the topic, or sway anyone's belief? It's the opposite of productive conversation, if you think they're encouraging a harmful or counterproductive dialogue then you can downvote them and move on. It's not rocket science.
