Analyzing Geekbench 6 under Intel's BOT

FYI, Geekbench 6 already optimizes for AVX512. Intel just optimizes it even more for them.

I'll take the side of Geekbench here. There is no reason for Intel to optimize a benchmark tool except to cheat.

userbinator 8 hours ago | parent | prev | next [-]

This suggests the checksum is used to identify whether the binary is known to BOT, and thus whether BOT can optimize the binary.

I do wonder what this "optimize" step actually entails; does it just replace the binary with one that Intel themselves carefully decompiled and then hand-optimised? If it's a general "decompile-analyse-optimise-recompile" (perhaps something similar to what the https://en.wikipedia.org/wiki/Transmeta_Crusoe does), why restrict it?

▲

boomanaiden154 8 hours ago | parent | prev | next [-]

Post link optimization (PLO) tools have been around for quite a while. In particular, Meta’s BOLT (fully upstream in LLVM) and Google’s Propeller (somewhat upstream in LLVM, but fully open source) have been around for 5+ years at this point.

It doesn’t seem like Intel’s BOT delivers more performance gains, and it is closed source.

▲

tyushk 8 hours ago | parent | next [-]

Intel BOT seems to be patches for specific binaries (hence why they didn't see a difference for Geekbench 6.7), unlike BOLT/Propeller which are for arbitrary programs. The second image from their help page [1] showcases this.

[1] https://www.intel.com/content/www/us/en/support/articles/000...

▲

userbinator 7 hours ago | parent | next [-]

Applying targeted binary patches shouldn't take 40 seconds... unless that's also a fake "so it looks like it's working really hard" delay.

▲

boomanaiden154 7 hours ago | parent | prev [-]

I might be thinking of a different project then...

I swore Intel had their own PLO tool, but I can only find https://github.com/clearlinux/distribution/issues/2996.

	▲	boomanaiden154 7 hours ago \| parent [-]
		Found it. It was https://www.phoronix.com/news/Intel-Thin-Layout-Optimizer. It was open source, but has since been deprecated.

▲

trynumber9 8 hours ago | parent | prev [-]

Question: do those vectorize code as in the example here? I was of the understanding they performed a more limited subset of optimizations.

	▲	boomanaiden154 7 hours ago \| parent [-]
		Propeller can’t really do many instruction level modifications due to how it works (constructs a layout file that then gets passed to the linker). BOLT could do this, but does not as far as I’m aware. Most of vectorization like this is also probably better done in a compiler middle end. At least in LLVM, the loop vectorizer and especially the SLP Vectorizer do a decent job of picking up most of the gains. You might be able to pick up some gains by doing it post-link at the MC level, but writing an IR level SLP Vectorizer is already quite difficult.

▲

tyushk 8 hours ago | parent | prev | next [-]

quack3.exe again in a way. If it's been done for years on GPU shaders, then why not CPU code?

	▲	consp 6 hours ago \| parent [-]
		While highly specific optimisations might give you a tiny bit of advantage, the main boost here is vector code which would work on any processor supporting the instructions. They could have looked at the vendor bits and use those to flag for optimization in any cpu but they didn't and limited it to a small subset of programs and cpus. It tingles the "PR above all else must have highest score" sense.

▲

whatever1 7 hours ago | parent | prev | next [-]

Can we also end user tune our cpus for specific tasks we do?

▲

refulgentis 8 hours ago | parent | prev [-]

> BOT optimizations are poorly documented, aggressive in scope, and damage comparability with other CPUs. For example, BOT allows Intel processors to run vector instructions while other processors continue to run scalar instructions. This provides an unfair advantage to Intel

Wait until they hear about branch predictors.

	▲	1una 4 hours ago \| parent [-]
		The thing is BOT only applies to a handful of applications. So Geekbench scores with BOT applied aren't as representative.