Perf improvement: single_query

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| single_query | Single Query Platform 8- Trends Database gold-win | 08/01/2026 12:50:44 | 728,474 | 748,079 | 2.69 % (19,605) :thumbsup: | 2.10 σ | 9,348.60 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-rc.1.26379.102` -> `11.0.0-rc.1.26381.101` https://github.com/dotnet/dotnet/compare/813f634ceb016018f5acc9bd3c2b16e17dff4686...45ee027fe6e3e41dfe3c747563bb5bf728768b97 Microsoft.AspNetCore.App `11.0.0-rc.1.26379.102` -> `11.0.0-rc.1.26381.101` https://github.com/dotnet/dotnet/compare/813f634ceb016018f5acc9bd3c2b16e17dff4686...45ee027fe6e3e41dfe3c747563bb5bf728768b97 Microsoft.NETCore.App `11.0.0-rc.1.26379.102` -> `11.0.0-rc.1.26381.101` https://github.com/dotnet/dotnet/compare/813f634ceb016018f5acc9bd3c2b16e17dff4686...45ee027fe6e3e41dfe3c747563bb5bf728768b97 |

[PowerBI Dashboard](https://aka.ms/aspnet/benchmarks)

@sebastienros

The report names only the single_query benchmark scenario and the PowerBI Dashboard; it provides no source file, test, or entry point to inspect. Start by reviewing that benchmark and its dependency changes, then establish the intended performance target before work begins; the payload does not define what done should be beyond comparing benchmark results.

Written by the indexing model from the issue text.