[osti]

Not true. Geekbench, especially single threaded benchmark, is probably the best we got, it has a bunch of workloads, unlike many other benchmarks like cinebench for example. And they publish all the results on their website, so you can dig into each individual workload and find the ones that apply to you.

And like the other poster mentioned, it correlates well with SPEC, so it's basically a easily accessible SPEC. These days the only benchmark I use to quickly judge some CPU is geekbench.

[dkechag]

May I suggest the one I use (I wrote it), which also correlates well with SPEC & Geekbench 5, but also runs the benchmarks on all cores if you want to so you get both max single-thread and max multi-thread: https://github.com/dkechag/dkbench-docker . You basically run 'docker run -it --rm dkechag/dkbench'.

[osti]

I took a look, it's not bad but it seems to contain too many micro benchmarks like regex or primes. Geekbench at least has clang which is a subscore that I always look at.

[dkechag]

The primes one is my least favourite one indeed, I left it in just because I happened to include it in the very first version and I am thinking it just counts for 5% in the end... The regex ones are "micro" yet quite important, dkbench it's a Perl (and C)-based benchmark (reflects our main code), and the regex engine is the most highly optimized part of the language so regex speed is a good representation of text processing speed in Perl. As I said, the overall score correlates well to SPEC/Geekbench so as a suite it works well. For compiler comparisons I usually compile a language like python or perl as a test, but I did not want to add something like that, to keep it fast with many smaller benchmarks.

[osti]

Actually yeah, I shouldn't have said that regex is a microbenchmark, it's indeed an important one.