Perf regression: caching, fortunes_dapper, fortunes_ef

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| caching | Caching Platform 20- Trends Database cobalt-hosted-lin-azl3-28 | 06/17/2026 23:41:39 | 321,878 | 232,569 | -27.75 % (-89,309) :thumbsdown: | -2.67 σ | 33,439.06 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-preview.6.26315.114` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/5d5112a4233a43ff41dacf791ec95d8b82ca980d...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 Microsoft.AspNetCore.App `11.0.0-preview.6.26315.114` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/5d5112a4233a43ff41dacf791ec95d8b82ca980d...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 Microsoft.NETCore.App `11.0.0-preview.6.26315.114` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/5d5112a4233a43ff41dacf791ec95d8b82ca980d...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 |
| fortunes_dapper | Fortunes Dapper 20- Trends Database cobalt-hosted-lin-azl3-28 | 06/17/2026 09:53:30 | 151,570 | 94,284 | -37.80 % (-57,286) :thumbsdown: | -2.84 σ | 20,176.75 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-preview.6.26315.107` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/d24fbbd5381f769b8d6c883fa9ea6bcf205a2136...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 Microsoft.AspNetCore.App `11.0.0-preview.6.26315.107` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/d24fbbd5381f769b8d6c883fa9ea6bcf205a2136...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 Microsoft.NETCore.App `11.0.0-preview.6.26315.107` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/d24fbbd5381f769b8d6c883fa9ea6bcf205a2136...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 |
| fortunes_ef | Fortunes EF 20- Trends Database cobalt-hosted-lin-azl3-28 | 06/17/2026 09:52:25 | 137,893 | 88,440 | -35.86 % (-49,453) :thumbsdown: | -2.91 σ | 16,965.51 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-preview.6.26315.107` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/d24fbbd5381f769b8d6c883fa9ea6bcf205a2136...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 Microsoft.AspNetCore.App `11.0.0-preview.6.26315.107` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/d24fbbd5381f769b8d6c883fa9ea6bcf205a2136...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 Microsoft.NETCore.App `11.0.0-preview.6.26315.107` -> `11.0.0-preview.6.26316.109` https://github.com/dotnet/dotnet/compare/d24fbbd5381f769b8d6c883fa9ea6bcf205a2136...a5012d3e7d616cd7f32f7e7d2e9e2ea06f33f117 |

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

@sebastienros

Start with the caching, fortunes_dapper, and fortunes_ef benchmark results and compare the dependency changes linked in the issue, especially the ASP.NET Core and .NET runtime commits. Use the PowerBI Dashboard to reproduce or inspect the regression across the listed scenarios. Done means the cause of the RPS drop is identified and the affected benchmark results return to an acceptable level.

Written by the indexing model from the issue text.