You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[.NET 10 vs main] CoreCLR performance regression tracking
This issue tracks the actionable CoreCLR results from the reviewed release/10.0 vs main windowed comparison. Draft generated 2026-08-17. GitHub issue/PR states refreshed from live metadata on 2026-08-17. User decisions and AI-attributed notes applied on 2026-08-17.
Use the checkboxes in place: leave an item unchecked while investigation, filing, ownership, or verification remains; check it when that work is finished. Feel free to edit or append status directly on the same checklist line as work progresses. There is intentionally no separate Completed section.
Within each section, items are ordered by worst reviewed percentage (largest first). Regression count is used only to break ties.
Excluded: fixed, acceptable, not-applicable, noise, improved, baseline-outlier, covered, and linked.
Actionable summary
Area
Items
Needs investigation (runtime + ungrouped missed)
37
Active tracked runtime regressions
13
Autofiling issues needing transfer/resolution
28
Missed regression date groups needing filing
9
Total checkboxes
87
Needs investigation
Show 37 items
Items requiring a second look before deciding whether to file, transfer, accept, or close them.
dotnet/runtime#125085 — needs-investigation; closed-completed; 162 CoreCLR reviewed regressions; worst +1122.4%; regression date 2026-02-20. Review note: Some regressions still real, many seem to have been noise. Need to double check System.Numerics.Tests.Perf_BigInteger and System.Collections.Concurrent.IsEmpty at least Representative chart.
dotnet/runtime#128998 — needs-investigation; closed-not-planned; 44 CoreCLR reviewed regressions; worst +1122.4%; regression date 2026-06-02. Review note: Many System.Buffers.Tests.RentReturnArrayPoolTests tests were (and are) regressed while this was closed as noise. AI Note: Verify whether sibling fix PR #126622 resolved the ArrayPool regressions before closing this tracker item. (evidence) Representative chart.
dotnet/runtime#129180 — acceptable; closed-completed; 36 CoreCLR reviewed regressions; worst +584.4%; regression date 2026-06-06. Review note: Still regressed, initial look into done, but last update was June 10th and not part of a milestone. AI Note (user-approved): Closed as an accepted Zen4 REX-prefix microarchitectural trade-off with no viable mitigation. (evidence) Representative chart.
dotnet/runtime#120068 — needs-investigation; closed-completed; 49 CoreCLR reviewed regressions; worst +132.3%; regression date 2025-09-22. Review note: Seems System.Collections.Concurrent.IsEmpty may still be hitting issues. Representative chart.
dotnet/runtime#125501 — not-applicable; closed-completed; 1 CoreCLR reviewed regressions; worst +110.2%; regression date 2026-03-10. Review note: Cause wasn't fully tracked down and it seems to now be bimodal. AI Note (user-approved): Closed after investigation concluded this was not an actual performance regression. (evidence) Representative chart.
dotnet/runtime#130697 — needs-investigation; open; 30 CoreCLR reviewed regressions; worst +95.0%; regression date 2026-07-08. Review note: Added to milestone but nothing new in a month or so Representative chart.
dotnet/runtime#125781 — needs-investigation; open; 7 CoreCLR reviewed regressions; worst +45.0%; regression date 2026-03-17. Review note: No real follow up since March Representative chart.
dotnet/runtime#129860 — needs-investigation; open; 90 CoreCLR reviewed regressions; worst +39.4%; regression date 2026-06-24. Review note: Still very real and no non-wasm work has started or been surfaced recently. Representative chart.
dotnet/runtime#126154 — fixed; closed-completed; 5 CoreCLR reviewed regressions; worst +35.2%; regression date 2026-03-23. Review note: Last updated Jun 9th. User update: Fixed and nearly unregressed. Representative chart.
dotnet/runtime#128908 — needs-investigation; open; 1 CoreCLR reviewed regressions; worst +34.6%; regression date 2026-05-27. Review note: Added to Milestone 11 and given Pri3 tag (July 9th) AI Note (user-approved): The owner committed to investigate after snap and keep the work in .NET 11. (evidence) Representative chart.
dotnet/runtime#129585 — needs-investigation; open; 1 CoreCLR reviewed regressions; worst +33.3%; regression date 2026-06-16. Review note: Added to Milestone 11 on June 18th, still real but no follow-up since. AI Note: The fix is known but was deprioritized to .NET 12. (evidence) Representative chart.
dotnet/runtime#131159 — acceptable; closed-completed; 25 CoreCLR reviewed regressions; worst +32.4%; regression date 2026-07-14. Review note: Seems related to the same change, both CoreCLR and Wasm-Mono seem regressed. AI Note (user-approved): Closed as an accepted trade-off from scoping vectorization away from browser/WASM. (evidence) Representative chart.
dotnet/runtime#126884 — needs-investigation; open; 12 CoreCLR reviewed regressions; worst +32.4%; regression date 2026-04-12. Review note: In Milestone 11, last activity is a question from April 17th. AI Note: Normalization overhead is now the leading root-cause mechanism and an owner is engaged. (evidence) Representative chart.
dotnet/runtime#118641 — needs-investigation; PR-merged; 3 CoreCLR reviewed regressions; worst +32.1%; regression date 2025-08-18. Review note: Weird bounce back and still real on some, though the regression amount is pretty small. Representative chart.
dotnet/runtime#129998 — needs-investigation; open; 4 CoreCLR reviewed regressions; worst +29.7%; regression date 2026-06-23. Review note: Moved to Milestone 11 on June 29th, but regressions are still real. Representative chart.
dotnet/runtime#128208 — needs-investigation; open; 3 CoreCLR reviewed regressions; worst +28.4%; regression date 2026-05-07. Review note: Added to Milestone 11 on May 15, no more follow-up. AI Note (user-approved): PR #127845 provided a partial fix; remaining work was deferred to .NET 12. (evidence) Representative chart.
dotnet/runtime#125504 — needs-investigation; closed-not-planned; 13 CoreCLR reviewed regressions; worst +26.9%; regression date 2026-03-07. Review note: Assigned 07/15 but no confirmation. The CrC seem to be the main issues. AI Note (user-approved): Closed not planned and deferred to Future; the root causes are known but no fix landed. (evidence) Representative chart.
dotnet/runtime#127230 — acceptable; closed-completed; 11 CoreCLR reviewed regressions; worst +26.8%; regression date 2026-04-18. Review note: Has initial investigation work started, but no updates since Jun 03 AI Note (user-approved): Closed as an expected early-inline trade-off; improvements outweighed regressions overall. (evidence) Representative chart.
dotnet/runtime#128710 — needs-investigation; closed-not-planned; 2 CoreCLR reviewed regressions; worst +20.3%; regression date 2026-05-20. Review note: Still real and no action post transfer (May 28th) AI Note (user-approved): Closed not planned; likely caused by PR #128303 and closed without a fix. (evidence) Representative chart.
dotnet/runtime#114996 — needs-investigation; closed-completed; 5 CoreCLR reviewed regressions; worst +17.6%; regression date 2026-04-27. Review note: Need to ensure System.Buffers.Tests.ReadOnlySequenceTests are being tracked elsewhere. Representative chart.
dotnet/runtime#127012 — not-applicable; closed-completed; 3 CoreCLR reviewed regressions; worst +17.6%; regression date 2026-04-09. Review note: Added to 11 milestone and last updated Apr 27. Probably should just be considered as part of general runtime async work. AI Note (user-approved): Closed after the movement was attributed to bimodal test behavior rather than a true regression. (evidence) Representative chart.
BenchmarksGame.Fasta_1.RunBench — needs-investigation; Ubuntu-arm64-Ampere; +17.4%; 581,025 → 682,015. Review note: No individual date seems to be the cause, just a slow decrease overtime.
dotnet/runtime#130044 — needs-investigation; open; 5 CoreCLR reviewed regressions; worst +10.3%; regression date 2026-06-25. Review note: Last updated nearly a month ago (investigation started though). AI Note: Assigned, marked as a bug, and milestoned to 11.0; no fix yet. (evidence) Representative chart.
IfStatements.IfStatements.OrArray — needs-investigation; Ubuntu-x64-Viper; +9.3%; 30,495 → 33,324. Review note: Nothing clear from the .NET 11 timeframe
dotnet/runtime#121413 — needs-investigation; closed-completed; 2 CoreCLR reviewed regressions; worst +8.1%; regression date 2025-10-28. Review note: Added to Milestone 11, no activity since then (Nov 24, 2025) AI Note (user-approved): State is closed-completed, but the closure rationale was not captured; verify before replacing needs-investigation with fixed. (evidence) Representative chart.
dotnet/runtime#123394 — needs-investigation; closed-completed; 1 CoreCLR reviewed regressions; worst +5.2%; regression date 2026-01-12. Review note: In Milestone 11 but no activity since Jan. AI Note (user-approved): GitHub is closed-completed, but no closure rationale was captured; verify before changing the mark. (evidence) Representative chart.
Active tracked regressions
Show 13 items
Existing runtime issues marked confirmed in the review. Treat every unchecked item here as a still-live regression, especially when its status has not been checked recently; check or edit the line when that changes.
dotnet/runtime#123159 — fixed; closed-completed; 43 CoreCLR reviewed regressions; worst +1122.4%; regression date 2026-01-06. Review note: Pretty sure some work is still being done for this. RentReturnArrayPoolTests seem to have unregressed from this change, Perf_File* slightly unregressed, but not all the way. User update: Fixed; checkbox should be checked in the public tracker. Representative chart.
dotnet/runtime#122186 — confirmed; closed-completed; 37 CoreCLR reviewed regressions; worst +1122.4%; regression date 2025-12-03. Review note: Still open and tracked (no recent updates). Many of the regressions seem unregressed, at least one System.Buffers.Tests.RentReturnArrayPoolTests<Object>.ProducerConsumer is still regressed above this issue. User update: RentReturnArrayPoolTests ProducerConsumer tests are still regressed. Representative chart.
dotnet/runtime#127326 — confirmed; closed-completed; 1 CoreCLR reviewed regressions; worst +164.7%; regression date 2026-04-13. Review note: Closed as not actionable, and wasn't a major regression contributor for the test. Representative chart.
dotnet/runtime#128594 — confirmed; open; 13 CoreCLR reviewed regressions; worst +129.9%; regression date 2026-05-21. Review note: Assigned 07/09, BigInt seems to be noise, Perf_Decimal is real. Representative chart.
dotnet/runtime#130309 — confirmed; open; 10 CoreCLR reviewed regressions; worst +99.6%; regression date 2026-07-03. Review note: In Milestone, last updated 3w ago. AI Note: Milestone moved from .NET 11 to .NET 12. (evidence) Representative chart.
dotnet/runtime#130418 — confirmed; open; 13 CoreCLR reviewed regressions; worst +55.4%; regression date 2026-07-06. Review note: Seems to be real, untriaged currently. AI Note (user-approved): Upgraded to confirmed; assigned, milestoned to 11.0, and an active PR is in progress. (evidence) Representative chart.
dotnet/runtime#117775 — confirmed; open; 3 CoreCLR reviewed regressions; worst +48.0%; regression date 2025-10-14. Review note: General Investigation added to 12 milestone AI Note (user-approved): Milestone moved from .NET 11 to .NET 12; mark and state remain confirmed/open. (evidence) Representative chart.
dotnet/runtime#123677 — confirmed; open; 15 CoreCLR reviewed regressions; worst +47.4%; regression date 2026-01-23. Review note: Still real, set to P3 on milestone 11 July 9th AI Note: Priority was raised to P1; the owner committed to post-snap .NET 11 investigation. (evidence) Representative chart.
dotnet/runtime#130041 — fixed; closed-completed; 18 CoreCLR reviewed regressions; worst +40.0%; regression date 2026-06-29. Review note: In milestone, last updated 3w ago. User update: Fix is not 100%, but the associated project was closed. Representative chart.
dotnet/runtime#119770 — confirmed; open; 18 CoreCLR reviewed regressions; worst +37.6%; regression date 2025-09-10. Review note: Transferred and in work queue for 11, marked pri2 07/09. Tests are still regressed. AI Note: Priority was raised to P1; the owner committed to post-snap investigation. (evidence) Representative chart.
dotnet/runtime#122592 — confirmed; closed-not-planned; 1 CoreCLR reviewed regressions; worst +21.1%; regression date 2025-12-11. Review note: This is basically just noise around this regression issue. Representative chart.
dotnet/runtime#128910 — confirmed; closed-completed; 3 CoreCLR reviewed regressions; worst +16.8%; regression date 2026-05-27. Review note: All linked regressions seem to just be noise. Representative chart.
Autofiling issues needing transfer or resolution
Show 28 items
Uncorrelated autofiling issues that are unmarked or marked needs-investigation.
dotnet/perf-autofiling-issues#76504 — needs-investigation; open; 38 CoreCLR reviewed regressions; worst +1122.4%; regression date 2026-07-13. Review note: AI Note: Bot triage found confirmed regressions but inconclusive bisection and a BDN confounder; Look Again remains appropriate. (evidence) Representative chart.
dotnet/perf-autofiling-issues#68192 — needs-investigation; open; 34 CoreCLR reviewed regressions; worst +584.4%; regression date 2026-01-25. Review note: System.Net.Security.Tests.SslStreamTests and System.IO.Tests.Perf_File.WriteAllText(size: 100) still seem to be regressed and real. AI Note: Re-triage disputes weak bisection but confirms live regressions. (evidence) Representative chart.
dotnet/perf-autofiling-issues#73304 — needs-investigation; open; 23 CoreCLR reviewed regressions; worst +132.3%; regression date 2026-05-19. Review note: Seems to be due to BDN update, only clear on System.Buffers.Text.Tests.Base64EncodeDecodeInPlaceTests.Base64EncodeInPlace tests. This is the tracking issue. Representative chart.
dotnet/perf-autofiling-issues#68328 — needs-investigation; open; 4 CoreCLR reviewed regressions; worst +129.9%; regression date 2026-01-21. Review note: Seems like this did cause some minor regressions that are still real. AI Note: Reopened with Look Again; verify the BigInteger regression remains observable. (evidence) Representative chart.
dotnet/perf-autofiling-issues#68908 — needs-investigation; open; 43 CoreCLR reviewed regressions; worst +95.0%; regression date 2026-02-11. Review note: Still has some regressions (BigInteger) and no linked runtime issue. Representative chart.
dotnet/perf-autofiling-issues#76511 — unmarked; open; 5 CoreCLR reviewed regressions; worst +80.4%; regression date 2026-07-13. Review note: AI Note: Pipe async regressions appear real; the bisection window should be widened before follow-up. (evidence) Representative chart.
dotnet/perf-autofiling-issues#74230 — needs-investigation; open; 4 CoreCLR reviewed regressions; worst +53.2%; regression date 2026-06-05. Review note: Initially marked as noise but seems likely to be real (reopened). Representative chart.
dotnet/perf-autofiling-issues#76145 — needs-investigation; open; 2 CoreCLR reviewed regressions; worst +48.8%; regression date 2026-07-12. Review note: AI Note: Reconfirmed as real and reopened; no owner or milestone yet. (evidence) Representative chart.
dotnet/perf-autofiling-issues#64411 — needs-investigation; open; 3 CoreCLR reviewed regressions; worst +40.0%; regression date 2025-10-21. Review note: System.Formats.Tar.Tests.Perf_TarWriter.UstarTarEntry_WriteEntry on Windows x64 is the only one applicable, it is still real. Representative chart.
dotnet/perf-autofiling-issues#71339 — needs-investigation; open; 10 CoreCLR reviewed regressions; worst +35.5%; regression date 2026-04-09. Review note: Still impacting Viper and seems uninvestigated at all. (Specifically System.Collections.Tests.Perf_PriorityQueue<Int32, Int32> at least) AI Note: The PriorityQueue regression was reconfirmed and sibling #71327 was linked. (evidence) Representative chart.
dotnet/perf-autofiling-issues#61218 — needs-investigation; open; 12 CoreCLR reviewed regressions; worst +33.3%; regression date 2025-08-21. Review note: Only System.Text.RegularExpressions.Tests.Perf_Regex_Industry_RustLang_Sherlock.Count(Pattern: "\w+", Options: Compiled) seems real and still regressed form this issue. User update: Keep needs-investigation; the Regex benchmark is still regressed. Representative chart.
dotnet/perf-autofiling-issues#62717 — needs-investigation; closed-completed; 4 CoreCLR reviewed regressions; worst +33.2%; regression date 2025-09-15. Review note: Marked as Likely PGO, but Ubuntu-x64-Viper are still regressed (and consistent), so may be real. Representative chart.
dotnet/perf-autofiling-issues#68008 — needs-investigation; open; 12 CoreCLR reviewed regressions; worst +30.8%; regression date 2026-01-22. Review note: System.Text.RegularExpressions.Tests.Perf_Regex_Industry_RustLang_Sherlock.Count(Pattern: "\w+", Options: NonBacktracking) still seems real. Mix of noise, improve, and regress overall. Representative chart.
dotnet/perf-autofiling-issues#73489 — needs-investigation; open; 1 CoreCLR reviewed regressions; worst +30.0%; regression date 2026-05-23. Review note: Reopened. Regex and HashSetContains seem to still be regressed, should investigate if it is PGO. AI Note: Reopened with a PGO/Ampere hypothesis; no confirmed cause or fix yet. (evidence) Representative chart.
dotnet/perf-autofiling-issues#74226 — needs-investigation; open; 1 CoreCLR reviewed regressions; worst +18.9%; regression date 2026-06-02. Review note: Initially closed as noise, but seem like they are real. AI Note: Conflicting Noise and reopened/possibly-real signals require human triage. (evidence) Representative chart.
dotnet/perf-autofiling-issues#70428 — needs-investigation; open; 2 CoreCLR reviewed regressions; worst +16.2%; regression date 2026-03-22. Review note: Only seems to be impacting Win-x64 User update: Keep needs-investigation; should be transferred to dotnet/runtime. Representative chart.
dotnet/perf-autofiling-issues#73927 — needs-investigation; open; 8 CoreCLR reviewed regressions; worst +14.8%; regression date 2026-05-28. Review note: System.Text.Json.Serialization.Tests.ReadJson<Nullable<DateTimeOffset>>.DeserializeFromStream(Mode: Reflection) seems to be real around now User update: Keep needs-investigation; should be transferred to dotnet/runtime. Representative chart.
dotnet/perf-autofiling-issues#72924 — needs-investigation; open; 3 CoreCLR reviewed regressions; worst +13.8%; regression date 2026-04-21. Review note: Seems to still be real and was real (72331 was closed as noise) Representative chart.
dotnet/perf-autofiling-issues#63745 — needs-investigation; closed-completed; 1 CoreCLR reviewed regressions; worst +12.5%; regression date 2025-10-07. Review note: Definitely a real little bump here. Marked as PGO, but it has continued up slightly. Representative chart.
dotnet/perf-autofiling-issues#67460 — needs-investigation; open; 3 CoreCLR reviewed regressions; worst +11.0%; regression date 2025-12-07. Review note: OrOr and Collection still seem to be real and caused around here. Representative chart.
Dated groups containing at least one needs-investigation or truly-missed regression. The checkbox represents the group as one candidate public tracking issue.
Regression group 2025-11-14 — 20 actionable of 20 related regressions; worst +21.1%; queues Win-x64-Viper. Review notes: 11/14/2025, 05/05/26ish | 11/14/2025
Regression group 2026-05-07 — 1 actionable of 1 related regressions; worst +9.7%; queues Ubuntu-arm64-Ampere. Review notes: Very noisy, without clear regression dates.
Regression group 2026-02-28 — 1 actionable of 1 related regressions; worst +7.0%; queues Win-x64-Viper. Review notes: No issues in range, but this was also a pretty new test.
[.NET 10 vs main] CoreCLR performance regression tracking
This issue tracks the actionable
CoreCLRresults from the reviewed release/10.0 vs main windowed comparison. Draft generated 2026-08-17. GitHub issue/PR states refreshed from live metadata on 2026-08-17. User decisions and AI-attributed notes applied on 2026-08-17.Use the checkboxes in place: leave an item unchecked while investigation, filing, ownership, or verification remains; check it when that work is finished. Feel free to edit or append status directly on the same checklist line as work progresses. There is intentionally no separate Completed section.
Within each section, items are ordered by worst reviewed percentage (largest first). Regression count is used only to break ties.
Inclusion rules
Included:
needs-investigation, confirmed runtime regressions, unmarked runtime/autofiling/missed items, and missed regressions markedtruly-missed.Excluded:
fixed,acceptable,not-applicable,noise,improved,baseline-outlier,covered, andlinked.Actionable summary
Needs investigation
Show 37 items
Items requiring a second look before deciding whether to file, transfer, accept, or close them.
dotnet/runtime#125085 — needs-investigation;
closed-completed; 162CoreCLRreviewed regressions; worst +1122.4%; regression date 2026-02-20. Review note: Some regressions still real, many seem to have been noise. Need to double check System.Numerics.Tests.Perf_BigInteger and System.Collections.Concurrent.IsEmpty at least Representative chart.dotnet/runtime#128998 — needs-investigation;
closed-not-planned; 44CoreCLRreviewed regressions; worst +1122.4%; regression date 2026-06-02. Review note: Many System.Buffers.Tests.RentReturnArrayPoolTests tests were (and are) regressed while this was closed as noise. AI Note: Verify whether sibling fix PR #126622 resolved the ArrayPool regressions before closing this tracker item. (evidence) Representative chart.dotnet/runtime#129180 — acceptable;
closed-completed; 36CoreCLRreviewed regressions; worst +584.4%; regression date 2026-06-06. Review note: Still regressed, initial look into done, but last update was June 10th and not part of a milestone. AI Note (user-approved): Closed as an accepted Zen4 REX-prefix microarchitectural trade-off with no viable mitigation. (evidence) Representative chart.dotnet/runtime#120068 — needs-investigation;
closed-completed; 49CoreCLRreviewed regressions; worst +132.3%; regression date 2025-09-22. Review note: Seems System.Collections.Concurrent.IsEmpty may still be hitting issues. Representative chart.dotnet/runtime#125501 — not-applicable;
closed-completed; 1CoreCLRreviewed regressions; worst +110.2%; regression date 2026-03-10. Review note: Cause wasn't fully tracked down and it seems to now be bimodal. AI Note (user-approved): Closed after investigation concluded this was not an actual performance regression. (evidence) Representative chart.dotnet/runtime#130697 — needs-investigation;
open; 30CoreCLRreviewed regressions; worst +95.0%; regression date 2026-07-08. Review note: Added to milestone but nothing new in a month or so Representative chart.dotnet/runtime#125781 — needs-investigation;
open; 7CoreCLRreviewed regressions; worst +45.0%; regression date 2026-03-17. Review note: No real follow up since March Representative chart.dotnet/runtime#129860 — needs-investigation;
open; 90CoreCLRreviewed regressions; worst +39.4%; regression date 2026-06-24. Review note: Still very real and no non-wasm work has started or been surfaced recently. Representative chart.System.Threading.Tests.Perf_CancellationToken.RegisterAndUnregister_Serial— needs-investigation;Ubuntu-arm64-Ampere; +39.3%; 40.7 → 56.7. Review note: Nearly recovered, maybe still a 1-4 % regression when bimodal noise is taken into account.dotnet/runtime#126154 — fixed;
closed-completed; 5CoreCLRreviewed regressions; worst +35.2%; regression date 2026-03-23. Review note: Last updated Jun 9th. User update: Fixed and nearly unregressed. Representative chart.dotnet/runtime#128908 — needs-investigation;
open; 1CoreCLRreviewed regressions; worst +34.6%; regression date 2026-05-27. Review note: Added to Milestone 11 and given Pri3 tag (July 9th) AI Note (user-approved): The owner committed to investigate after snap and keep the work in .NET 11. (evidence) Representative chart.dotnet/runtime#129585 — needs-investigation;
open; 1CoreCLRreviewed regressions; worst +33.3%; regression date 2026-06-16. Review note: Added to Milestone 11 on June 18th, still real but no follow-up since. AI Note: The fix is known but was deprioritized to .NET 12. (evidence) Representative chart.dotnet/runtime#131159 — acceptable;
closed-completed; 25CoreCLRreviewed regressions; worst +32.4%; regression date 2026-07-14. Review note: Seems related to the same change, both CoreCLR and Wasm-Mono seem regressed. AI Note (user-approved): Closed as an accepted trade-off from scoping vectorization away from browser/WASM. (evidence) Representative chart.dotnet/runtime#126884 — needs-investigation;
open; 12CoreCLRreviewed regressions; worst +32.4%; regression date 2026-04-12. Review note: In Milestone 11, last activity is a question from April 17th. AI Note: Normalization overhead is now the leading root-cause mechanism and an owner is engaged. (evidence) Representative chart.dotnet/runtime#118641 — needs-investigation;
PR-merged; 3CoreCLRreviewed regressions; worst +32.1%; regression date 2025-08-18. Review note: Weird bounce back and still real on some, though the regression amount is pretty small. Representative chart.dotnet/runtime#129998 — needs-investigation;
open; 4CoreCLRreviewed regressions; worst +29.7%; regression date 2026-06-23. Review note: Moved to Milestone 11 on June 29th, but regressions are still real. Representative chart.dotnet/runtime#128208 — needs-investigation;
open; 3CoreCLRreviewed regressions; worst +28.4%; regression date 2026-05-07. Review note: Added to Milestone 11 on May 15, no more follow-up. AI Note (user-approved): PR #127845 provided a partial fix; remaining work was deferred to .NET 12. (evidence) Representative chart.dotnet/runtime#125504 — needs-investigation;
closed-not-planned; 13CoreCLRreviewed regressions; worst +26.9%; regression date 2026-03-07. Review note: Assigned 07/15 but no confirmation. The CrC seem to be the main issues. AI Note (user-approved): Closed not planned and deferred to Future; the root causes are known but no fix landed. (evidence) Representative chart.dotnet/runtime#127230 — acceptable;
closed-completed; 11CoreCLRreviewed regressions; worst +26.8%; regression date 2026-04-18. Review note: Has initial investigation work started, but no updates since Jun 03 AI Note (user-approved): Closed as an expected early-inline trade-off; improvements outweighed regressions overall. (evidence) Representative chart.dotnet/runtime#128710 — needs-investigation;
closed-not-planned; 2CoreCLRreviewed regressions; worst +20.3%; regression date 2026-05-20. Review note: Still real and no action post transfer (May 28th) AI Note (user-approved): Closed not planned; likely caused by PR #128303 and closed without a fix. (evidence) Representative chart.dotnet/runtime#114996 — needs-investigation;
closed-completed; 5CoreCLRreviewed regressions; worst +17.6%; regression date 2026-04-27. Review note: Need to ensure System.Buffers.Tests.ReadOnlySequenceTests are being tracked elsewhere. Representative chart.dotnet/runtime#127012 — not-applicable;
closed-completed; 3CoreCLRreviewed regressions; worst +17.6%; regression date 2026-04-09. Review note: Added to 11 milestone and last updated Apr 27. Probably should just be considered as part of general runtime async work. AI Note (user-approved): Closed after the movement was attributed to bimodal test behavior rather than a true regression. (evidence) Representative chart.BenchmarksGame.Fasta_1.RunBench— needs-investigation;Ubuntu-arm64-Ampere; +17.4%; 581,025 → 682,015. Review note: No individual date seems to be the cause, just a slow decrease overtime.System.Collections.ContainsKeyTrue<Int32, Int32>.ImmutableDictionary(Size: 512)— needs-investigation;Win-x64-Viper; +13.3%; 3,773 → 4,276. Review note: Very noisy and mostly sideways, but the noisiness bounds shrink for an unclear reason.dotnet/runtime#130044 — needs-investigation;
open; 5CoreCLRreviewed regressions; worst +10.3%; regression date 2026-06-25. Review note: Last updated nearly a month ago (investigation started though). AI Note: Assigned, marked as a bug, and milestoned to 11.0; no fix yet. (evidence) Representative chart.IfStatements.IfStatements.OrArray— needs-investigation;Ubuntu-x64-Viper; +9.3%; 30,495 → 33,324. Review note: Nothing clear from the .NET 11 timeframeSystem.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName(input: typeof(System.Collections.Generic.Dictionary<String, Boolean>))— needs-investigation;Win-x64-Viper; +8.9%; 2,040 → 2,222. Review note: Got worse over time, nothing clear.System.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName(input: typeof(int))— needs-investigation;Win-x64-Viper; +8.8%; 647.6 → 704.8. Review note: Got worse over time, nothing clear.System.IO.Tests.Perf_Path.GetFullPathNoRedundantSegments— needs-investigation;Win-x64-Viper; +8.3%; 174.2 → 188.6. Review note: Very noisy, without clear regression dates.System.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName(input: typeof(System.Int32[,]))— needs-investigation;Win-x64-Viper; +8.2%; 700.1 → 757.2. Review note: Got worse over time, nothing clear.dotnet/runtime#121413 — needs-investigation;
closed-completed; 2CoreCLRreviewed regressions; worst +8.1%; regression date 2025-10-28. Review note: Added to Milestone 11, no activity since then (Nov 24, 2025) AI Note (user-approved): State is closed-completed, but the closure rationale was not captured; verify before replacing needs-investigation with fixed. (evidence) Representative chart.System.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName(input: typeof(System.Int32*))— needs-investigation;Win-x64-Viper; +6.8%; 682.5 → 729.1. Review note: Got worse over time, nothing clear.[
System.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName(input: typeof(System.Collections.Generic.Dictionary2[]))](https://pvscmdupload.z22.web.core.windows.net/reports/allTestHistory/refs/heads/main_x64_Windows%2010.0.22631/ViperWindows/System.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName%28input%3A%20typeof%28System.Collections.Generic.Dictionary%602%5B%5D%29%29.html) — **needs-investigation**;Win-x64-Viper`; +6.7%; 2,120 → 2,263. Review note: Got worse over time, nothing clear.System.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName(input: typeof(System.Int32&))— needs-investigation;Win-x64-Viper; +6.6%; 686.8 → 732.0. Review note: Got worse over time, nothing clear.[
System.Reflection.Metadata.Perf_TypeName.ParseAndGetFullName(input: typeof(System.Collections.Generic.Dictionary2[]))](https://pvscmdupload.z22.web.core.windows.net/reports/allTestHistory/refs/heads/main_x64_Windows%2010.0.22631/ViperWindows/System.Reflection.Metadata.Perf_TypeName.ParseAndGetFullName%28input%3A%20typeof%28System.Collections.Generic.Dictionary%602%5B%5D%29%29.html) — **needs-investigation**;Win-x64-Viper`; +6.6%; 1,532 → 1,632. Review note: Got worse over time, nothing clear.System.Reflection.Metadata.Perf_TypeName.ParseAndGetAssemblyQualifiedName(input: typeof(System.Int32[*]))— needs-investigation;Win-x64-Viper; +5.6%; 697.4 → 736.6. Review note: Got worse over time, nothing clear.dotnet/runtime#123394 — needs-investigation;
closed-completed; 1CoreCLRreviewed regressions; worst +5.2%; regression date 2026-01-12. Review note: In Milestone 11 but no activity since Jan. AI Note (user-approved): GitHub is closed-completed, but no closure rationale was captured; verify before changing the mark. (evidence) Representative chart.Active tracked regressions
Show 13 items
Existing runtime issues marked
confirmedin the review. Treat every unchecked item here as a still-live regression, especially when its status has not been checked recently; check or edit the line when that changes.dotnet/runtime#123159 — fixed;
closed-completed; 43CoreCLRreviewed regressions; worst +1122.4%; regression date 2026-01-06. Review note: Pretty sure some work is still being done for this. RentReturnArrayPoolTests seem to have unregressed from this change, Perf_File* slightly unregressed, but not all the way. User update: Fixed; checkbox should be checked in the public tracker. Representative chart.dotnet/runtime#122186 — confirmed;
closed-completed; 37CoreCLRreviewed regressions; worst +1122.4%; regression date 2025-12-03. Review note: Still open and tracked (no recent updates). Many of the regressions seem unregressed, at least one System.Buffers.Tests.RentReturnArrayPoolTests<Object>.ProducerConsumer is still regressed above this issue. User update: RentReturnArrayPoolTests ProducerConsumer tests are still regressed. Representative chart.dotnet/runtime#127326 — confirmed;
closed-completed; 1CoreCLRreviewed regressions; worst +164.7%; regression date 2026-04-13. Review note: Closed as not actionable, and wasn't a major regression contributor for the test. Representative chart.dotnet/runtime#128594 — confirmed;
open; 13CoreCLRreviewed regressions; worst +129.9%; regression date 2026-05-21. Review note: Assigned 07/09, BigInt seems to be noise, Perf_Decimal is real. Representative chart.dotnet/runtime#130309 — confirmed;
open; 10CoreCLRreviewed regressions; worst +99.6%; regression date 2026-07-03. Review note: In Milestone, last updated 3w ago. AI Note: Milestone moved from .NET 11 to .NET 12. (evidence) Representative chart.dotnet/runtime#119499 — confirmed;
closed-completed; 29CoreCLRreviewed regressions; worst +71.1%; regression date 2025-09-04. Review note: Still some minor regression, but mostly unregressed by Improve performance of IsCollectible reflection properties runtime#119743 (still maybe a 10-15% regression for most it seems). Representative chart.dotnet/runtime#130418 — confirmed;
open; 13CoreCLRreviewed regressions; worst +55.4%; regression date 2026-07-06. Review note: Seems to be real, untriaged currently. AI Note (user-approved): Upgraded to confirmed; assigned, milestoned to 11.0, and an active PR is in progress. (evidence) Representative chart.dotnet/runtime#117775 — confirmed;
open; 3CoreCLRreviewed regressions; worst +48.0%; regression date 2025-10-14. Review note: General Investigation added to 12 milestone AI Note (user-approved): Milestone moved from .NET 11 to .NET 12; mark and state remain confirmed/open. (evidence) Representative chart.dotnet/runtime#123677 — confirmed;
open; 15CoreCLRreviewed regressions; worst +47.4%; regression date 2026-01-23. Review note: Still real, set to P3 on milestone 11 July 9th AI Note: Priority was raised to P1; the owner committed to post-snap .NET 11 investigation. (evidence) Representative chart.dotnet/runtime#130041 — fixed;
closed-completed; 18CoreCLRreviewed regressions; worst +40.0%; regression date 2026-06-29. Review note: In milestone, last updated 3w ago. User update: Fix is not 100%, but the associated project was closed. Representative chart.dotnet/runtime#119770 — confirmed;
open; 18CoreCLRreviewed regressions; worst +37.6%; regression date 2025-09-10. Review note: Transferred and in work queue for 11, marked pri2 07/09. Tests are still regressed. AI Note: Priority was raised to P1; the owner committed to post-snap investigation. (evidence) Representative chart.dotnet/runtime#122592 — confirmed;
closed-not-planned; 1CoreCLRreviewed regressions; worst +21.1%; regression date 2025-12-11. Review note: This is basically just noise around this regression issue. Representative chart.dotnet/runtime#128910 — confirmed;
closed-completed; 3CoreCLRreviewed regressions; worst +16.8%; regression date 2026-05-27. Review note: All linked regressions seem to just be noise. Representative chart.Autofiling issues needing transfer or resolution
Show 28 items
Uncorrelated autofiling issues that are unmarked or marked
needs-investigation.dotnet/perf-autofiling-issues#76504 — needs-investigation;
open; 38CoreCLRreviewed regressions; worst +1122.4%; regression date 2026-07-13. Review note: AI Note: Bot triage found confirmed regressions but inconclusive bisection and a BDN confounder; Look Again remains appropriate. (evidence) Representative chart.dotnet/perf-autofiling-issues#73440 — linked;
closed-completed; 39CoreCLRreviewed regressions; worst +584.4%; regression date 2026-05-19. Review note: Seems to be due to BDN update, only clear on System.Buffers.Text.Tests.Base64EncodeDecodeInPlaceTests.Base64EncodeInPlace tests. Connected to [Perf] Linux/arm64: 86 Regressions on 5/19/2026 5:33:16 PM +00:00 perf-autofiling-issues#73304 User update: Linked to perf-autofiling-issues#73304. Representative chart.dotnet/perf-autofiling-issues#68192 — needs-investigation;
open; 34CoreCLRreviewed regressions; worst +584.4%; regression date 2026-01-25. Review note: System.Net.Security.Tests.SslStreamTests and System.IO.Tests.Perf_File.WriteAllText(size: 100) still seem to be regressed and real. AI Note: Re-triage disputes weak bisection but confirms live regressions. (evidence) Representative chart.dotnet/perf-autofiling-issues#76327 — unmarked;
closed-completed; 30CoreCLRreviewed regressions; worst +584.4%; regression date 2026-07-14. Representative chart.dotnet/perf-autofiling-issues#73485 — noise;
closed-completed; 7CoreCLRreviewed regressions; worst +164.7%; regression date 2026-05-19. Review note: Seems to be due to BDN update, only clear on System.Buffers.Text.Tests.Base64EncodeDecodeInPlaceTests.Base64EncodeInPlace tests. Connected to [Perf] Linux/arm64: 86 Regressions on 5/19/2026 5:33:16 PM +00:00 perf-autofiling-issues#73304 AI Note (user-approved): Reclassified as a BDN-update measurement artifact and closed. (evidence) Representative chart.dotnet/perf-autofiling-issues#69630 — needs-investigation;
open; 6CoreCLRreviewed regressions; worst +139.0%; regression date 2026-02-25. Review note: Still real and seems uninvestigated. Representative chart.dotnet/perf-autofiling-issues#73304 — needs-investigation;
open; 23CoreCLRreviewed regressions; worst +132.3%; regression date 2026-05-19. Review note: Seems to be due to BDN update, only clear on System.Buffers.Text.Tests.Base64EncodeDecodeInPlaceTests.Base64EncodeInPlace tests. This is the tracking issue. Representative chart.dotnet/perf-autofiling-issues#68328 — needs-investigation;
open; 4CoreCLRreviewed regressions; worst +129.9%; regression date 2026-01-21. Review note: Seems like this did cause some minor regressions that are still real. AI Note: Reopened with Look Again; verify the BigInteger regression remains observable. (evidence) Representative chart.dotnet/perf-autofiling-issues#68908 — needs-investigation;
open; 43CoreCLRreviewed regressions; worst +95.0%; regression date 2026-02-11. Review note: Still has some regressions (BigInteger) and no linked runtime issue. Representative chart.dotnet/perf-autofiling-issues#76511 — unmarked;
open; 5CoreCLRreviewed regressions; worst +80.4%; regression date 2026-07-13. Review note: AI Note: Pipe async regressions appear real; the bisection window should be widened before follow-up. (evidence) Representative chart.dotnet/perf-autofiling-issues#74230 — needs-investigation;
open; 4CoreCLRreviewed regressions; worst +53.2%; regression date 2026-06-05. Review note: Initially marked as noise but seems likely to be real (reopened). Representative chart.dotnet/perf-autofiling-issues#76145 — needs-investigation;
open; 2CoreCLRreviewed regressions; worst +48.8%; regression date 2026-07-12. Review note: AI Note: Reconfirmed as real and reopened; no owner or milestone yet. (evidence) Representative chart.dotnet/perf-autofiling-issues#64411 — needs-investigation;
open; 3CoreCLRreviewed regressions; worst +40.0%; regression date 2025-10-21. Review note: System.Formats.Tar.Tests.Perf_TarWriter.UstarTarEntry_WriteEntry on Windows x64 is the only one applicable, it is still real. Representative chart.dotnet/perf-autofiling-issues#71339 — needs-investigation;
open; 10CoreCLRreviewed regressions; worst +35.5%; regression date 2026-04-09. Review note: Still impacting Viper and seems uninvestigated at all. (Specifically System.Collections.Tests.Perf_PriorityQueue<Int32, Int32> at least) AI Note: The PriorityQueue regression was reconfirmed and sibling #71327 was linked. (evidence) Representative chart.dotnet/perf-autofiling-issues#61218 — needs-investigation;
open; 12CoreCLRreviewed regressions; worst +33.3%; regression date 2025-08-21. Review note: Only System.Text.RegularExpressions.Tests.Perf_Regex_Industry_RustLang_Sherlock.Count(Pattern: "\w+", Options: Compiled) seems real and still regressed form this issue. User update: Keep needs-investigation; the Regex benchmark is still regressed. Representative chart.dotnet/perf-autofiling-issues#62717 — needs-investigation;
closed-completed; 4CoreCLRreviewed regressions; worst +33.2%; regression date 2025-09-15. Review note: Marked as Likely PGO, but Ubuntu-x64-Viper are still regressed (and consistent), so may be real. Representative chart.dotnet/perf-autofiling-issues#68008 — needs-investigation;
open; 12CoreCLRreviewed regressions; worst +30.8%; regression date 2026-01-22. Review note: System.Text.RegularExpressions.Tests.Perf_Regex_Industry_RustLang_Sherlock.Count(Pattern: "\w+", Options: NonBacktracking) still seems real. Mix of noise, improve, and regress overall. Representative chart.dotnet/perf-autofiling-issues#71327 — needs-investigation;
open; 9CoreCLRreviewed regressions; worst +30.4%; regression date 2026-04-09. Review note: Related to 71339 Representative chart.dotnet/perf-autofiling-issues#73489 — needs-investigation;
open; 1CoreCLRreviewed regressions; worst +30.0%; regression date 2026-05-23. Review note: Reopened. Regex and HashSetContains seem to still be regressed, should investigate if it is PGO. AI Note: Reopened with a PGO/Ampere hypothesis; no confirmed cause or fix yet. (evidence) Representative chart.dotnet/perf-autofiling-issues#63385 — needs-investigation;
open; 14CoreCLRreviewed regressions; worst +18.9%; regression date 2025-09-29. Review note: Had been marked look again, still real. Representative chart.dotnet/perf-autofiling-issues#74226 — needs-investigation;
open; 1CoreCLRreviewed regressions; worst +18.9%; regression date 2026-06-02. Review note: Initially closed as noise, but seem like they are real. AI Note: Conflicting Noise and reopened/possibly-real signals require human triage. (evidence) Representative chart.dotnet/perf-autofiling-issues#70428 — needs-investigation;
open; 2CoreCLRreviewed regressions; worst +16.2%; regression date 2026-03-22. Review note: Only seems to be impacting Win-x64 User update: Keep needs-investigation; should be transferred to dotnet/runtime. Representative chart.dotnet/perf-autofiling-issues#70026 — needs-investigation;
open; 5CoreCLRreviewed regressions; worst +14.8%; regression date 2026-03-09. Representative chart.dotnet/perf-autofiling-issues#73927 — needs-investigation;
open; 8CoreCLRreviewed regressions; worst +14.8%; regression date 2026-05-28. Review note: System.Text.Json.Serialization.Tests.ReadJson<Nullable<DateTimeOffset>>.DeserializeFromStream(Mode: Reflection) seems to be real around now User update: Keep needs-investigation; should be transferred to dotnet/runtime. Representative chart.dotnet/perf-autofiling-issues#72924 — needs-investigation;
open; 3CoreCLRreviewed regressions; worst +13.8%; regression date 2026-04-21. Review note: Seems to still be real and was real (72331 was closed as noise) Representative chart.dotnet/perf-autofiling-issues#63745 — needs-investigation;
closed-completed; 1CoreCLRreviewed regressions; worst +12.5%; regression date 2025-10-07. Review note: Definitely a real little bump here. Marked as PGO, but it has continued up slightly. Representative chart.dotnet/perf-autofiling-issues#67460 — needs-investigation;
open; 3CoreCLRreviewed regressions; worst +11.0%; regression date 2025-12-07. Review note: OrOr and Collection still seem to be real and caused around here. Representative chart.dotnet/perf-autofiling-issues#75686 — needs-investigation;
open; 1CoreCLRreviewed regressions; worst +6.1%; regression date 2026-06-29. Review note: Seems to still be real Representative chart.Missed regression groups needing filing
Show 9 items
Dated groups containing at least one
needs-investigationortruly-missedregression. The checkbox represents the group as one candidate public tracking issue.Regression group 2025-11-14 — 20 actionable of 20 related regressions; worst +21.1%; queues
Win-x64-Viper. Review notes: 11/14/2025, 05/05/26ish | 11/14/2025System.Reflection.Attributes.IsDefinedClassMissInherit—Win-x64-Viper; +21.1%; 531.9 → 644.0; mark needs-investigation; note: 11/14/2025, 05/05/26ishExceptions.Handling.TryAndFinallyDeep(kind: Software)—Win-x64-Viper; +18.0%; 6,129 → 7,230; mark needs-investigation; note: 11/14/2025Exceptions.Handling.TryAndFinallyDeep(kind: Hardware)—Win-x64-Viper; +16.8%; 7,546 → 8,813; mark needs-investigation; note: 11/14/2025System.Reflection.Attributes.GetCustomAttributesMethodOverrideHit—Win-x64-Viper; +16.5%; 753.1 → 877.5; mark needs-investigation; note: 11/14/2025System.Reflection.Attributes.GetCustomAttributesMethodOverrideHitInherit—Win-x64-Viper; +14.4%; 1,282 → 1,467; mark needs-investigation; note: 11/14/2025System.Reflection.Attributes.GetCustomAttributesMethodOverrideMiss—Win-x64-Viper; +14.2%; 757.8 → 865.7; mark needs-investigation; note: 11/14/2025Regression group 2026-06-23 — 2 actionable of 2 related regressions; worst +20.5%; queues
Win-x64-Viper. Review notes: Possibly related to [Perf] Linux/x64: 32 Regressions on 6/4/2025 5:12:34 PM +00:00 runtime#116486 but this was closed while the regression is still real.Microsoft.Extensions.DependencyInjection.ActivatorUtilitiesBenchmark.CreateInstance_3_WithAttrLast—Win-x64-Viper; +20.5%; 79.6 → 96.0; mark needs-investigation; note: Possibly related to [Perf] Linux/x64: 32 Regressions on 6/4/2025 5:12:34 PM +00:00 runtime#116486 but this was closed while the regression is still real.Microsoft.Extensions.DependencyInjection.ActivatorUtilitiesBenchmark.CreateInstance_3_WithAttrFirst—Win-x64-Viper; +19.4%; 79.8 → 95.3; mark needs-investigation; note: Possibly related to [Perf] Linux/x64: 32 Regressions on 6/4/2025 5:12:34 PM +00:00 runtime#116486 but this was closed while the regression is still real.Regression group 2026-01-06 — 2 actionable of 2 related regressions; worst +16.2%; queues
Ubuntu-x64-Viper,Win-x64-Viper.BenchmarksGame.Fasta_1.RunBench—Win-x64-Viper; +16.2%; 261,339 → 303,804; mark needs-investigationBenchmarksGame.Fasta_1.RunBench—Ubuntu-x64-Viper; +5.3%; 302,386 → 318,461; mark needs-investigationRegression group 2026-05-12 — 1 actionable of 1 related regressions; worst +10.5%; queues
Win-x64-Viper.System.Collections.CtorFromCollection<Int32>.ImmutableDictionary(Size: 512)—Win-x64-Viper; +10.5%; 51,061 → 56,438; mark needs-investigationRegression group 2026-05-07 — 1 actionable of 1 related regressions; worst +9.7%; queues
Ubuntu-arm64-Ampere. Review notes: Very noisy, without clear regression dates.System.IO.Tests.Perf_Path.GetFullPathWithRedundantSegments—Ubuntu-arm64-Ampere; +9.7%; 1,522 → 1,670; mark needs-investigation; note: Very noisy, without clear regression dates.Regression group 2026-05-30 — 1 actionable of 1 related regressions; worst +9.3%; queues
Ubuntu-arm64-Ampere. Review notes: Around 05/29-30System.Text.RegularExpressions.Tests.Perf_Regex_Common.Uri_IsNotMatch(Options: Compiled)—Ubuntu-arm64-Ampere; +9.3%; 105.7 → 115.6; mark needs-investigation; note: Around 05/29-30Regression group 2026-04-23 — 4 actionable of 4 related regressions; worst +8.8%; queues
Ubuntu-x64-Viper,Win-x64-Viper.ArrayDeAbstraction.foreach_static_readonly_array_via_interface—Win-x64-Viper; +8.8%; 144.9 → 157.6; mark needs-investigationArrayDeAbstraction.foreach_static_readonly_array_via_interface_property—Win-x64-Viper; +8.8%; 144.9 → 157.7; mark needs-investigationArrayDeAbstraction.foreach_static_readonly_array_via_interface—Ubuntu-x64-Viper; +8.5%; 145.2 → 157.5; mark needs-investigationArrayDeAbstraction.foreach_static_readonly_array_via_interface_property—Ubuntu-x64-Viper; +8.1%; 146.1 → 157.9; mark needs-investigationRegression group 2026-04-18 — 1 actionable of 1 related regressions; worst +7.8%; queues
Win-x64-Viper.System.Diagnostics.Perf_EventSource.Log—Win-x64-Viper; +7.8%; 137.1 → 147.7; mark needs-investigationRegression group 2026-02-28 — 1 actionable of 1 related regressions; worst +7.0%; queues
Win-x64-Viper. Review notes: No issues in range, but this was also a pretty new test.System.Text.RegularExpressions.Tests.Perf_Regex_Industry_Rebar_Russian.Count(Pattern: "(?i)Шерлок Холмс|Джон Уотсон|Ирен Адлер|инспектор Лестрейд|профессор Мориарти", Options: NonBacktracking)—Win-x64-Viper; +7.0%; 9,930,484 → 10,625,815; mark needs-investigation; note: No issues in range, but this was also a pretty new test.