Skip to content

docs: match the C3 dependency-injector ratio to the table #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lesnik512 merged 1 commit into from
Oct 3, 2026
Merged

docs: match the C3 dependency-injector ratio to the table #551

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/introduction/performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ _Across-run IQR of each side's own median (5 runs): modern-di ≤1.1%, rivals
## What the numbers show

- Against `dependency-injector`, modern-di is faster by reference on C1 (**0.42**) and
C3 (**0.37**), and far faster on the batched C4 request lifecycle (**0.02**).
C3 (**0.36**), and far faster on the batched C4 request lifecycle (**0.02**).
dependency-injector's C4 body calls `init_resources()`/`shutdown_resources()` every cycle
in addition to resolving; the suite doesn't decompose how much of its per-request cost is
that lifecycle work versus the resolve itself, so C4 should be read as a whole-lifecycle
Expand Down
Loading