-
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] Windows/x64: 3 Regressions on 6/3/2024 10:30:18 PM #103296
Comments
Commit range: 2a80808...1e0c243 Slightly suspect this PR: #101020 |
Tagging subscribers to this area: @dotnet/area-system-io |
Other potentially related regressions: Linux x64: dotnet/perf-autofiling-issues#36053 |
Moving to area-System.Runtime since it seems to be related to the recent |
@adamsitnik, which changes? I'm missing it in the diff. |
I relied on this comment: #103296 (comment) |
Interesting... that's not the same as the diff link at the top of the post: c6bfb06...9a3d45a |
It's also suspect that a commit which just changed |
@LoopedBard3 where did you get that range from? Which one is the correct one, yours or c6bfb06...9a3d45a (the one next to Diff)? |
I grabbed that range manually using the graph in the [1, 1] ReadLine test history link as it had the clearest regression point for comparison. Looking at the [9, 32] Readline history, there may be something also around the diff range next to Diff. Part of the reason for this difference is that the autofiling tool is making a best effort for both linking issues together by commit time and in figuring out the commits to blame. There is also a minor regression in the listed commit range it seems for the [1, 1] ReadLine test history but it immediately went back to the expected result. |
After a long git bisect, c95d3b8 seems to be culprit cc @mangod9 @janvorli @eduardo-vp @jkotas
|
some of these microbenchmark regressions are expected with CET enabled as discussed here: #103654 |
Comparing c286a8e (commit older than any visible regression) versus main+revert of c95d3b8:
Looks like c95d3b8 is the only significant regression. Closing. |
Run Information
Regressions in System.IO.Tests.StringReaderReadLineTests
Test Report
Repro
General Docs link: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md
System.IO.Tests.StringReaderReadLineTests.ReadLineAsync(LineLengthRange: [ 1, 8])
ETL Files
Histogram
JIT Disasms
System.IO.Tests.StringReaderReadLineTests.ReadLine(LineLengthRange: [ 9, 32])
ETL Files
Histogram
JIT Disasms
System.IO.Tests.StringReaderReadLineTests.ReadLine(LineLengthRange: [ 1, 1])
ETL Files
Histogram
JIT Disasms
Docs
Profiling workflow for dotnet/runtime repository
Benchmarking workflow for dotnet/runtime repository
The text was updated successfully, but these errors were encountered: