Replies: 1 comment
-
Yes, you can read more about similar settings in our docs public static void Main(string[] args)
{
var config = ManualConfig.CreateMinimumViable()
.AddJob(Job.ShortRun
.WithEvaluateOverhead(false)); //
BenchmarkSwitcher.FromAssembly(typeof(Program).Assembly).Run(args, config);
}
No, it's currently not supported and I really doubt that we ever do that. If you are searching for ways to reduce the time it takes to run the benchmarks you can check this config that is used by the official .NET benchmarking repo: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For
ShortRunJob
s the calculation of the overhead often takes longer than the calculation of the workload itself. In addition, the overhead of just a few nanoseconds is in many cases negligible anyway.Is it possible to skip the calculation of the overhead?
Is it possible to cache and reuse the overhead of functions with the same signature?
In my case I have like 10 function with the same signature that will be run with a number of parameters.
For every iteration a new calculation of the overhead is performed that comes basically to the same result.
Beta Was this translation helpful? Give feedback.
All reactions