Skip to content

Clarify the Performance section benchmarks directory mode #161

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

Closed
stijnvanhulle wants to merge 1 commit into from
Closed

Clarify the Performance section benchmarks directory mode #161

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
6 changes: 5 additions & 1 deletion docs/5.x/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -699,7 +699,11 @@ v5 generates code faster than v4, and the gap widens as the spec grows. The numb
[`scripts/benchmark/v4-vs-v5`](https://github.com/kubb-labs/kubb/tree/main/scripts/benchmark/v4-vs-v5)
in the kubb repository, a harness anyone can run and reproduce. It benchmarks `@kubb/core@4.39.2`
against the v5 beta (`@kubb/core@5.0.0-beta.104`, plugins at `5.0.0-beta.103`), median of three runs
per configuration, both versions writing to a fresh directory so the comparison stays apples-to-apples.
per configuration, both versions writing to a fresh directory. Every plugin runs in directory mode
(one file per schema or operation, `output.mode: 'directory'`) on both versions, so the comparison
stays apples-to-apples. Output mode changes the numbers substantially: switching both versions to
kubb's default file mode instead makes both v4 and v5 slower, but it costs v5 disproportionately
more, so the speedup shrinks to a smaller, flatter number that no longer grows with spec size.

<SpeedComparison />

Expand Down