-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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.Text.RegularExpressions.Tests.Perf_Regex_Industry_Mariomkas #67915
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. |
ubuntu-x64 dotnet/perf-autofiling-issues#4523 |
Thanks. This one is expected. We had an unbounded memory leak due to a static cache, which I deleted. This test is measuring construction time, so the change essentially reverted the ctor cost to what it should have been all along, rather than reusing the objects from a previous construction of the exact same regex. |
(Interestingly, though, it results in a significant improvement in construction time if, over time, you end up creating lots of different regexes, as then you see the full negative impact of the unbounded cache. We have a test that constructs several thousand different regexes, and that improved by ~3x.) |
Windows-Arm64: dotnet/perf-autofiling-issues#4616 |
Ubuntu-Arm64: dotnet/perf-autofiling-issues#4627 |
Win-x64: dotnet/perf-autofiling-issues#4573 |
Windows x64: dotnet/perf-autofiling-issues#4606 |
Run Information
Regressions in System.Text.RegularExpressions.Tests.Perf_Regex_Industry_Mariomkas
Test Report
Repro
Payloads
Baseline
Compare
Histogram
System.Text.RegularExpressions.Tests.Perf_Regex_Industry_Mariomkas.Ctor(Pattern: "[\w.+-]+@[\w.-]+.[\w.-]+", Options: NonBacktracking)
Description of detection logic
Description of detection logic
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: