According to Geekbench a 9900K also beats a Ryzen 3700X in Clang. However when those two CPUs actually face head to head in an actual compilation benchmark (such as compiling LLVM), the 3700X easily & consistently beats the 9900K: https://openbenchmarking.org/embed.php?i=1907064-HV-CPUBENCH...
And these are both 8-core / 16-thread CPUs, no multi-thread brute force shenanigans. And the 3700X is even the lower TDP & lower measured power consumption part, so no sketchy turbo games either.
So don't put too much faith in Geekbench numbers. They seem to have a very weak relationship to reality.
> Clang is a compiler front end for the programming languages C, C++, Objective-C,
Objective-C++, OpenMP, OpenCL, and CUDA. It uses LLVM as its back end.
The Clang workload compiles a 1,094 line C source file (of which 729 lines are code). The
workload uses AArch64 as the target architecture for code generation.
729 LOC within a single file doesn't represent ANYTHING about real world compilation. It neatly fits within a single system call and the entire thing fits within L2 cache (maybe even within L1 cache).
Why did you choose to ignore the 2.22x faster multi-core score of the 9900k?
Tests like these are also very questionable if they are constrained to sub-60s microbenchmarks, which ignore power-limits and cooling.
I'd rather wait for the actual product in a comparable package (e.g. laptop chassis vs. whatever unspecified environment the Geekbench test was run in) before drawing conclusions...
Nobody's drawing conclusions here. All I'm saying is that it isn't crazy to think that an A14 part will be competitive with Intel's lineup, especially from a core performance perspective.
Power limits and memory hierarchy both benefit the 9900k heavily in this comparison, which is why I went with the single-core score. I'd be surprised if an iPhone 11 Pro Max will floor all its cores even for a short microbenchmark. A desktop/laptop A14 will likely look much more competitive in these respects.
> The Multicore benchmark compares a 8 core with a dualcore which is a bad faith comparison.
How so? Are we comparing real-world performance or artificially limited what-if-scenarios? That's my critique with these benchmarks in general.
I don't care what a single A13/A14 BIG-core does in a short burst load situation when the context is code compilation that takes a minute or more on a system with multiple cores.
Multi-core is a bad faith comparison you say? I'd say it's an Apples-to-apples comparison if anything, since I usually don't artificially restrict my machine when trying to get work done as fast as possible.
So I'd argue that it's actually your perspective that's just theoretical: oh look - this dual-core [technically hexa-core while we're on the topic of being theoretical] SoC is faster than this octa-core, provided we choose a short, bursty workload and limit ourselves to a single core. You know, as one does when compiling Chrome or a any big software...
Like, contexts where compilation times actually matter as supposed to compiling this small utility takes only 0.89s on the A13X as opposed to 1.2s on the i9. I know, I know, the difference adds up quickly, like to an whole hour after just 11600 compilations. Theoretically, that is. sigh
> How so? Are we comparing real-world performance or artificially limited what-if-scenarios? That's my critique with these benchmarks in general.
Remember the point of this thread: speculating on how fast ARM chips will be for compilation workloads compared to Intel chips when shipped as part of Macbooks. It seems that you are mistaking the point of the parent poster - nobody is arguing that an iPhone is better at compiling code than a desktop with an i9 chip.
The comparison of an 8-core chip to a current 2-core chip is pointless because it is an artifact of comparing a $500 stand-alone chip to a chip that is sold as part of a complete $400 phone. Adding more cores is easy - it just costs more money, and Apple has opted not to do it for the iPhone because it is not necessary for standard iPhone workloads.
It is a very reasonable assumption that the chip that will ship with a Macbook will have at least as many cores (but probably more as the individual cores are cheaper) than the equivalent Intel chip.
> I don't care what a single A13/A14 BIG-core does in a short burst load situation when the context is code compilation that takes a minute or more on a system with multiple cores.
ARM chips are more energy efficient and run less hot than Intel chips. In an equivalent chassis they have the advantage in this situation. The intel chip will overheat and throttle faster.
> So I'd argue that it's actually your perspective that's just theoretical: oh look - this dual-core [technically hexa-core while we're on the topic of being theoretical] SoC is faster than this octa-core, provided we choose a short, bursty workload and limit ourselves to a single core. You know, as one does when compiling Chrome or a any big software...
Again, it's speculation. Obviously it's theoretical. The point is that current benchmarks indicate that ARM chips are very good for compilation workloads - relatively comparable to Intel chips for a much lower cost.
