From 5e292ec89b4fbad3ad47f75ebdadc5b5c4fffa00 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Valentin=20Breu=C3=9F?= Date: Wed, 8 Jul 2026 19:15:53 +0200 Subject: [PATCH] docs: lead benchmarks with the Realistic scenario and drop Size=64 Make Realistic the first and default tab, since it is the most representative workload, and update the methodology note to the current container sizes (8 and 256) now that the Size=64 case has been retired from the suite. --- Docs/pages/11-benchmarks.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/Docs/pages/11-benchmarks.mdx b/Docs/pages/11-benchmarks.mdx index 97652ae..6b09ce0 100644 --- a/Docs/pages/11-benchmarks.mdx +++ b/Docs/pages/11-benchmarks.mdx @@ -21,33 +21,33 @@ Awaiten wires the graph at build time, so there is nothing to reflect over at ru - **Job**: `MediumRun` with the in-process toolchain. - **Runner**: `ubuntu-latest` GitHub Actions agent, refreshed on every push to `main`. - Each row shows time and allocated memory, sorted fastest-first; bars are scaled within the row so length corresponds to magnitude. The Awaiten row is highlighted as the baseline (`1.00x`) and every other row shows its ratio relative to Awaiten. **Lower is better.** -- Click a row to hide that container so the others spread out. Build and Resolve are measured at container sizes of 8, 64, and 256 registrations; switch between them with the inline tabs. +- Click a row to hide that container so the others spread out. Build and Resolve are measured at container sizes of 8 and 256 registrations; switch between them with the inline tabs. ::: - + -Steady-state resolution of a service by type once the container is built. +A per-request pattern, the shape a web app actually runs: open a scope, resolve a deep graph of mixed lifetimes rooted at a request handler, then dispose the scope. - + - + -Container construction from cold, over a graph of singletons. +Steady-state resolution of a service by type once the container is built. - + - + -A per-request pattern, the shape a web app actually runs: open a scope, resolve a deep graph of mixed lifetimes rooted at a request handler, then dispose the scope. +Container construction from cold, over a graph of singletons. - +