- For practical use, and non overclocked, the EC12 at 5.5 Ghz: https://www.redbooks.ibm.com/redbooks/pdfs/sg248049.pdf
or
- An AMD FX-8370 floating in Liquid Nitrogen at 8.7 Ghz: https://hwbot.org/benchmark/cpu_frequency/rankings#start=0#i...
- For practical use, and non overclocked, the EC12 at 5.5 Ghz: https://www.redbooks.ibm.com/redbooks/pdfs/sg248049.pdf
or
- An AMD FX-8370 floating in Liquid Nitrogen at 8.7 Ghz: https://hwbot.org/benchmark/cpu_frequency/rankings#start=0#i...
https://physics.stackexchange.com/questions/348854/parker-so...
When people talk about a supercomputer being 'fast' they generally mean FLOPS - floating point operations per seconds, which isn't clock-speed.
Multiplying the number of processors by the clock speed of the processors, and then multiplying that product by the number of floating-point operations the processors can perform in one second, as done for supercomputers FLOPS, does not help me :-)
I was trolling a little bit, the people who downvoted my measure of speed :-) because the millions of FLOPS of a supercomputer, will help for parallel tasks but will not be "faster" for a common use case.
So fastest computer is one thing, most powerful is another.
Your argument is a bit like saying the fastest land speed vehicle isn't really the fastest because you can't go to the grocery store with it.
And why should your algorithm be the benchmark for supercomputer performance, rather than something that is at least somewhat related [1] to the workloads those machines run?
[1] We can of course argue endlessly that HPL is no longer a very representative benchmark for supercomputer workloads, but I digress.
Nobody but you is confused about this.
Ultimately, however, no system is measured by its clock rate- or by its cache size- or by its MIPS. Because no real workload is truly determined by a simple linear function of those variables.
Time to completion will depend on task.
The video below compares 8150 against CPUs from 2020 (i.e. no 5900x or 12900KS), includes data from 8370.