Perf improvement: fortunes, fortunes_dapper, fortunes_ef
- 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 |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| fortunes | Fortunes Platform 19- Trends Database Cobalt Hosted Lin Server | 12/18/2025 09:06:52 | 183,232 | 228,818 | 24.88 % (45,586) :thumbsup: | 2.58 σ | 17,682.32 | Changes NameVersionDiff |
| fortunes_dapper | Fortunes Platform Dapper 19- Trends Database Cobalt Hosted Lin Server | 12/18/2025 09:09:11 | 143,904 | 233,141 | 62.01 % (89,237) :thumbsup: | 2.89 σ | 30,914.45 | Changes NameVersionDiff |
| fortunes_ef | Fortunes Platform EF 19- Trends Database Cobalt Hosted Lin Server | 12/18/2025 09:08:04 | 145,919 | 219,755 | 50.60 % (73,836) :thumbsup: | 3.87 σ | 19,054.42 | Changes NameVersionDiff |
[PowerBI Dashboard](https://aka.ms/aspnet/benchmarks)
@sebastienros
Contributor guide
Research direction
The issue only reports benchmark results for the fortunes, fortunes_dapper, and fortunes_ef scenarios; it names no files, tests, or entry points. Start by locating those benchmark scenarios and reproducing the reported runs. Confirm the intended optimization and acceptance criteria before making changes, since the issue does not state what should be changed or when the work is done.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100