-
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
Regressions in System.MathBenchmarks.Double #85985
Comments
The commit range is 6f19e37...da0aa0c. |
There is some new T0 code in the diffs for the regression (such as But for the actual test code in question, there is no assembly diffs, just a couple small disasm formatting diffs |
Tagging subscribers to this area: @dotnet/area-system-runtime Issue DetailsRun Information
Regressions in System.MathBenchmarks.Double
ReproGeneral Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md Payloadsgit clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net8.0 --filter 'System.MathBenchmarks.Double*' PayloadsHistogramSystem.MathBenchmarks.Double.Sqrt
Description of detection logic
JIT DisasmsDocsProfiling workflow for dotnet/runtime repository
|
No codegen differences. Only difference is BDN changed how many operations its executing CC. @adamsitnik |
I am not sure if I follow. BDN estimates how many invocations should be performed per iteration (250ms), it almost always changes between runs but this should not have a big impact on the reported time. |
There were 0 changes to codegen for the actual benchmark itself between base and diff, the only actual change is that we have some more methods (on the general startup path) that start in T0, rather than starting in T1 (were no longer marked We semi-regularly see cases like this in the weekly triage. We also see cases where BDN doesn't work as expected with functions that have very small execution times (dotnet/BenchmarkDotNet#1802), which in turn can impact the overhead measurement of an empty call. The methods that are actually being measured can be seen by searching for |
Run Information
Regressions in System.MathBenchmarks.Double
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
Payloads
Baseline
Compare
Payloads
Baseline
Compare
Histogram
System.MathBenchmarks.Double.Sqrt
Description of detection logic
JIT Disasms
Baseline
Compare
Diff
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: