Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not possible to compute the (Ratio, RatioSD) #2591

Closed
AndreyAkinshin opened this issue Jul 20, 2024 Discussed in #2584 · 1 comment · Fixed by #2650
Closed

Not possible to compute the (Ratio, RatioSD) #2591

AndreyAkinshin opened this issue Jul 20, 2024 Discussed in #2584 · 1 comment · Fixed by #2650

Comments

@AndreyAkinshin
Copy link
Member

Discussed in #2584

Originally posted by sastru July 2, 2024
image

I get the warning

// * Warnings *
BaselineCustomAnalyzer
Summary -> A question mark '?' symbol indicates that it was not possible to compute the (Ratio, RatioSD) column(s) because the baseline value is too close to zero.

I suspect it is because somehow all my benchmarks are separated by a line, why? how can I fix that?

Program.cs

BenchmarkRunner.Run<Benchmarks>(DefaultConfig.Instance
    .AddJob(Job.InProcess
        .WithStrategy(RunStrategy.Monitoring)
        .DontEnforcePowerPlan()
        .WithToolchain(new InProcessEmitToolchain(true))
    ), args);

Benchmarks.cs

...
[Benchmark(Baseline = true)]
[Arguments(1028, 1028, false, OutsideQueryVariation.Default, false, null, 30)]
public async Task Baseline(int limit, int totalCount, bool includeOutsidePoints, OutsideQueryVariation useOutsideQueryVariation, bool useMaxOutsideInterval, int? status, int timeSpanInMin) { .. }

[Benchmark]
[Arguments(1028,  1028,  false, OutsideQueryVariation.Default,  false, 192,  30)]
[Arguments(1028,  1030,  true,  OutsideQueryVariation.Default,  false, null, 30)]
public async Task Benchmark(int limit, int totalCount, bool includeOutsidePoints, OutsideQueryVariation useOutsideQueryVariation, bool useMaxOutsideInterval, int? status, int timeSpanInMin) { .. }
```</div>
@timcassell
Copy link
Collaborator

Let's use this issue to track fixing the warning message. Use #2596 to track improving the usability of baselines with arguments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants