Perf improvement: fortunes, fortunes, fortunes_dapper
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 290
Description
| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| fortunes | Fortunes Razor Pages 14- Trends Database cobalt-cloud-lin-azl3 | 08/22/2026 00:41:31 | 21,818 | 24,142 | 10.65 % (2,324) :thumbsup: | 5.48 σ | 423.97 | Changes NameVersionDiff |
| fortunes | Fortunes Minimal APIs 19- Trends Database cobalt-hosted-lin | 08/22/2026 02:27:34 | 128,310 | 181,152 | 41.18 % (52,842) :thumbsup: | 2.12 σ | 24,891.51 | Changes NameVersionDiff |
| fortunes_dapper [Fixed] | Fortunes Platform Dapper 14- Trends Database cobalt-cloud-lin-azl3 | 08/22/2026 00:26:43 | 42,119 | 46,077 | 9.40 % (3,958) :thumbsup: | 3.66 σ | 1,081.37 | Changes NameVersionDiff |
[PowerBI Dashboard](https://aka.ms/aspnet/benchmarks)
@sebastienros
Contributor guide
Research direction
Start by reviewing the fortunes, Fortunes Minimal APIs, and fortunes_dapper benchmark entries and the linked PowerBI Dashboard. The issue names no source files, tests, entry point, performance target, or code change, so a maintainer would need to define the scope before completion can be assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100