-
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
[Perf] Regression on 8/1/2022 6:03:22 PM #73630
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. |
Tagging subscribers to this area: @dotnet/gc Issue DetailsRun Information
Regressions in System.Tests.Perf_GC<Char>
Reprogit clone https://github.com/dotnet/performance.git
py .\performance\scripts\benchmarks_ci.py -f net6.0 --filter 'System.Tests.Perf_GC<Char>*' PayloadsHistogramSystem.Tests.Perf_GC<Char>.AllocateUninitializedArray(length: 10000, pinned: False)
Description of detection logic
DocsProfiling workflow for dotnet/runtime repository
|
The change seems to be within the typical range for this particular test? |
I agree with @mangod9, I think this issue might be noisy with respect to #72923. I merged the PR ~9:30 AM PST for which the next point in the trend seemed to be at a similar previous level: Consequent regressions took place after the commit with the inflection point being on 8/3: It seems like the moving average also indicates similar behavior: Could this be related to some other commit? |
Closing this older Regions related issues, since they have been investigated. |
Run Information
Regressions in System.Tests.Perf_GC<Char>
Test Report
Repro
Payloads
Baseline
Compare
Histogram
System.Tests.Perf_GC<Char>.AllocateUninitializedArray(length: 10000, pinned: False)
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: