-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Gradual regression of System.Buffers.Tests.ReadOnlySequenceTests<Char>.IterateGetPositionArray from net6.0 to net7.0-rc2 #77028
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsThis benchmark has been jumping up and down throughout the whole net7.0 cycle but looking at the 6.0 data point seems like it gradually regressed. Benchmark results from 7.0-RC2 vs 6.0: System.Buffers.Tests.ReadOnlySequenceTests.IterateGetPositionArray
|
I'll take a look. |
Locally I see only a small regression: BenchmarkDotNet=v0.13.1.1847-nightly, OS=Windows 11 (10.0.22621.674) PowerPlanMode=00000000-0000-0000-0000-000000000000 IterationTime=250.0000 ms MaxIterationCount=20
Profiling (7.0) shows: |
x64 windows codegen for Codegen for However, just realized this is an x64 ubuntu issue, not a windows one. FWIW windows perf does not show this slow creep: So let me redo some of the above looking at ubuntu x64 codegen. |
Subsequently has improved again, and now faster than it's been; likely explanation was the pgo update in #85275 |
This benchmark has been jumping up and down throughout the whole net7.0 cycle but looking at the 6.0 data point seems like it gradually regressed.
Link to the chart:
https://pvscmdupload.blob.core.windows.net/reports/allTestHistory/refs/heads/main_x64_ubuntu%2018.04/System.Buffers.Tests.ReadOnlySequenceTests(Char).IterateGetPositionSingleSegment.html
Screenshot:
![newplot](https://user-images.githubusercontent.com/16040868/195715976-c32e7165-2ea8-4c19-b0e9-5833af51fd63.png)
Benchmark results from 7.0-RC2 vs 6.0:
System.Buffers.Tests.ReadOnlySequenceTests.IterateGetPositionArray
The text was updated successfully, but these errors were encountered: