aspnet/Benchmarks
Benchmarks for ASP.NET Core observed · 2026-09-03
Health v2 · maintenance only
77/100
- Activity 100
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4109
- days_rel: n/a
- days_push: 0
- n_releases_24m: 0
Adoption not part of the score
1192 stars · 244 forks observed · 2026-09-03
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A collection of benchmark applications and Docker images for measuring ASP.NET Core performance, including TechEmpower Web Framework Benchmarks scenarios. It is run by the ASP.NET team as a continuous benchmarking effort using Microsoft Crank.
Use cases
- benchmark asp.net core web framework performance
- run techempower benchmark scenarios locally
- set up continuous performance benchmarking pipelines
- compare http server throughput across dotnet versions
- load test asp.net core endpoints with crank
When to choose
- you need official ASP.NET Core performance baselines
- you want to reproduce TechEmpower scenarios for .NET
- you are setting up continuous benchmarking with Crank
When to avoid
- you need benchmarks for non-.NET web frameworks
- you want simple micro-benchmarks rather than full HTTP scenarios
Facets
application · maturity active
benchmarking http-server web-framework web-development performance backend dotnet cloud windows aspnet-core techempower crank continuous-benchmarking csharp docker linux
1 source
- readme: https://github.com/aspnet/Benchmarks · fetched 2026-09-03 · 16ced66d13a0
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| aspnet/Benchmarks | main | 77 |
For agents
markdown · JSON · MCP: product_card(name="aspnet/Benchmarks")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem