Run only MemoryDiagnoser, not performance diagnoser (warmup etc.) - to speed up execution #2451
Unanswered
MihaMarkic
asked this question in
Q&A
Replies: 1 comment 1 reply
-
I would like to say dry job, but due to tiered jit, it can give inaccurate results (see #1962). I recommend short job to get accurate results quickly. If your benchmark is long-running, such that it executes fewer than ~30 times, even short job won't give you accurate results (unless you actually want to measure tier0 allocations). You could also try disabling tiered jit, which I haven't tried myself. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys,
What would be the best way to avoid warmups and whatnot when only memory diagnostics is required?
Beta Was this translation helpful? Give feedback.
All reactions