dotnet / dotnet/aspnetcore

Perf regression: multiple_queries, updates

Open
#68,071 0 comments 0 reactions 0 assignees View on GitHub
area-perf perf-regression
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| multiple_queries [Fixed] | Multiple Queries Minimal APIs 20- Trends Database cobalt-hosted-lin-28 | 07/27/2026 12:02:00 | 21,640 | 14,990 | -30.73 % (-6,650) :thumbsdown: | -2.62 σ | 2,540.05 | Changes NameVersionDiff |
| updates | Updates Platform 14- Trends Database cobalt-cloud-lin-azl3 | 07/27/2026 13:08:01 | 4,530 | 3,983 | -12.07 % (-547) :thumbsdown: | -5.11 σ | 107.04 | Changes NameVersionDiff |

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

@sebastienros

Contributor guide

Open the contributing guide

Research direction

Start with the PowerBI Dashboard linked in the issue and compare the multiple_queries and updates benchmark runs. Investigate the reported RPS regressions and their associated benchmark changes; done means the regression is explained and a verified result shows whether performance has recovered.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.