-
Notifications
You must be signed in to change notification settings - Fork 5k
Regressions in System.Tests.Perf_Decimal on 2/17/2023 #82440
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
Comments
@MihaZupan seems to be caused by #82264. Not a super important regression, but it might be worth looking into why your PR would cause this to regress. We are guessing that another JIT optimization was reliant on the previous range check somehow. |
Tagging subscribers to this area: @dotnet/area-system-runtime Issue DetailsRun Information
Regressions in System.Tests.Perf_Decimal
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.Tests.Perf_Decimal*' PayloadsHistogramSystem.Tests.Perf_Decimal.ToString(value: 123456.789)
Description of detection logic
DocsProfiling workflow for dotnet/runtime repository
|
Closing. The regression was since fixed and we're now faster than before (50ns, rather than 57ns) |
Run Information
Regressions in System.Tests.Perf_Decimal
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.Tests.Perf_Decimal.ToString(value: 123456.789)
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: