You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: mention Jitting phase in How it works (#2942)
* docs: mention Jitting phase in How it works
* docs: add JittingStage to pseudocode
* Update docs/articles/guides/how-it-works.md
---------
Co-authored-by: Tim Cassell <[email protected]>
Copy file name to clipboardExpand all lines: docs/articles/guides/how-it-works.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@ BenchmarkDotNet follows the following steps to run your benchmarks:
6
6
2. Next, we take each method/job/params combination and try to measure its performance by launching benchmark process several times (`LaunchCount`).
7
7
3. An invocation of the workload method is an *operation*. A bunch of operation is an *iteration*. If you have an `IterationSetup` method, it will be invoked before each iteration,
8
8
but not between operations. We have the following type of iterations:
9
+
* `Jitting`: The overhead/workload methods are invoked to ensure they are JIT-compiled (and on tiered runtimes, to promote them when possible). These iterations are not used for measurements.
9
10
* `Pilot`: The best operation count will be chosen.
10
11
* `OverheadWarmup`, `OverheadWorkload`: BenchmarkDotNet overhead will be evaluated.
0 commit comments