For some configs, we start to collect profiling information and/or trigger a compilation later. The IR framework should take that into consideration when warming up tests such that IR matching operates on the same profiling information regardless of the configuration. The @Warmup annotation should still override any default value.

From https://github.com/openjdk/jdk/pull/5903#issuecomment-957885052:

As for the default warmup, I would probably expose CompilationPolicy::min_invocations() through the WB API and do the warmup based on that. There are a lot of ways different flags may affect the thresholds, I think we just need an authoritative API point to tell us the minimum number of invocations. I would also disable various feedback mechanisms in the policy to make it more deterministic. So, Tier4LoadFeedback=1000000, Tier3LoadFeedback=1000000, Tier3DelayOn=1000000, Tier0Delay=1000000, TieredCompileTaskTimeout=1000000; or we should add a single option to disable all adaptive features.