There wasn’t an option for nuance/other. Stabilizer doesn’t sound like something you’d want to tack onto a benchmarking library directly because it transforms the LLVM compiler to add the randomization instructions. That means we’d compile a typical version or a randomized version with some tweaked signature (latter probably done by some macro call), but there’s not a whole lot of point to keeping the second one around when benchmarking is done. It seems simpler to do the randomized benchmarking in a separate process where everything is randomized by a compiler option, it won’t just affect benchmark tools. The setup option of BenchmarkTools already lets you rerun code between samples, and that should have the effect of shuffling some code and heap addresses (so far we’ve only seen a benchmark for the latter). But anything beyond that should be an orthogonal compiler option IMO.
Apparently this just controls user-space priority, and there are higher priorities for realtime processes. No idea why there isn’t just 1 scale.