-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Regression in IfStatements.IfStatements #79101
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
@SingleAccretion Could this have been caused by #76491? |
It is hard for me to see how it could, though there is nothing else in the commit diff. There are no Linux ARM64 diffs for this benchmark in #76491 and the change only affects code using vectors. |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsRun Information
Regressions in IfStatements.IfStatements
Reprogit clone https://github.com/dotnet/performance.git
python3 .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'IfStatements.IfStatements*' PayloadsHistogramIfStatements.IfStatements.OrOr
Description of detection logic
DocsProfiling workflow for dotnet/runtime repository
|
@AndyAyersMS PTAL. |
This test was bimodal, and then regressed when PGO was enabled So this does not appear to be a regression per se (commit list shows nothing relevant). That later regression seems possibly to be a similar problem to #87194 (comment) -- with PGO we inline the if-convertable method into a loop? Looking cross-plat things looks similar elsewhere |
Run Information
Regressions in IfStatements.IfStatements
Test Report
Repro
Payloads
Baseline
Compare
Histogram
IfStatements.IfStatements.OrOr
Description of detection logic
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: