docs: update query benchmarks (3.9.0) #852
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,8 @@ Latencies are median over 5 runs. Hub target = most-connected node. | |
|
|
||
| | Version | Engine | fnDeps d1 | fnDeps d3 | fnDeps d5 | fnImpact d1 | fnImpact d3 | fnImpact d5 | diffImpact | | ||
| |---------|--------|----------:|----------:|----------:|------------:|------------:|------------:|-----------:| | ||
| | 3.9.0 | native | 27.4 ↑182% | 27.5 ↑178% | 27.5 ↑184% | 4 ↑11% | 4 ↑11% | 4 ↑14% | 9.3ms ↑4% | | ||
| | 3.9.0 | wasm | 26.9 ↑177% | 26.9 ↑174% | 26.9 ↑177% | 4 ↑14% | 4 ↑14% | 3.9 ↑8% | 7.9ms ↑8% | | ||
|
Comment on lines
+8
to
+9
Contributor
There was a problem hiding this comment.
In the 3.9.0 row, the native (Rust) engine posts 27.4ms for
Contributor
There was a problem hiding this comment. Addressed in the same Note (3.9.0) added in commit 6fa6e54. The note documents that the native-vs-WASM difference for fnDeps (27.4ms vs 26.9ms, ~2%) is within measurement noise and not a meaningful inversion. Both engines show the same magnitude of regression, which points to codebase growth rather than a native-specific issue. |
||
| | 3.7.0 | native | 9.7 ↑3% | 9.9 ↑3% | 9.7 ↑3% | 3.6 ↑6% | 3.6 ↑6% | 3.5 ↑6% | 8.9ms ↑7% | | ||
| | 3.7.0 | wasm | 9.7 ~ | 9.8 ~ | 9.7 ~ | 3.5 ↑3% | 3.5 ↑3% | 3.6 ↑6% | 7.3ms ↓19% | | ||
|
Comment on lines
10
to
11
Contributor
There was a problem hiding this comment.
The table jumps directly from 3.9.0 to 3.7.0, with no 3.8.0 row. Prior gaps in the history (e.g. 3.5.0 missing native data) are explained with a note. If 3.8.0 was a released version, its absence should be explained — either with a note (e.g. the workflow was not triggered, or was skipped for that release), or with a placeholder row. If 3.8.0 was never released, this is fine and no change is needed, but a brief note would help future readers interpret the version sequence.
Contributor
There was a problem hiding this comment. Addressed in the same Note (3.9.0) added in commit 6fa6e54. The note explains: v3.8.0 had no separate query benchmark run, and v3.8.1 query data was removed because it was measured before the |
||
| | 3.6.0 | native | 9.4 | 9.6 | 9.4 | 3.4 | 3.4 | 3.3 | 8.3ms | | ||
|
|
@@ -43,39 +45,39 @@ Latencies are median over 5 runs. Hub target = most-connected node. | |
|
|
||
| ### Latest results | ||
|
|
||
| **Version:** 3.9.0 | **Date:** 2026-04-04 | ||
|
|
||
| #### Native (Rust) | ||
|
|
||
| **Targets:** hub=`buildGraph`, mid=`node`, leaf=`docs` | ||
|
|
||
| | Metric | Value | | ||
| |--------|------:| | ||
| | fnDeps depth 1 | 27.4ms | | ||
| | fnDeps depth 3 | 27.5ms | | ||
| | fnDeps depth 5 | 27.5ms | | ||
| | fnImpact depth 1 | 4ms | | ||
| | fnImpact depth 3 | 4ms | | ||
| | fnImpact depth 5 | 4ms | | ||
| | diffImpact latency | 9.3ms | | ||
| | diffImpact affected functions | 0 | | ||
| | diffImpact affected files | 0 | | ||
|
|
||
| #### WASM | ||
|
|
||
| **Targets:** hub=`buildGraph`, mid=`node`, leaf=`docs` | ||
|
|
||
| | Metric | Value | | ||
| |--------|------:| | ||
| | fnDeps depth 1 | 26.9ms | | ||
| | fnDeps depth 3 | 26.9ms | | ||
| | fnDeps depth 5 | 26.9ms | | ||
| | fnImpact depth 1 | 4ms | | ||
| | fnImpact depth 3 | 4ms | | ||
| | fnImpact depth 5 | 3.9ms | | ||
| | diffImpact latency | 7.9ms | | ||
| | diffImpact affected functions | 0 | | ||
| | diffImpact affected files | 0 | | ||
|
|
||
| <!-- NOTES_START --> | ||
|
|
||
|
|
@@ -90,7 +92,56 @@ Latencies are median over 5 runs. Hub target = most-connected node. | |
| **Note (3.3.1):** The ↑157-192% fnDeps/fnImpact deltas for 3.3.1 vs 3.3.0 are not comparable. PR #528 changed the hub target from auto-selected `src/types.ts` (shallow type-barrel) to pinned `buildGraph` (deep orchestration function with 2-3x more edges). There is no engine regression — `diffImpact` improved 20-44% in the same release. Future version comparisons (3.3.1+) are stable and meaningful. | ||
| <!-- NOTES_END --> | ||
|
|
||
| <!-- QUERY_BENCHMARK_DATA | ||
| [ | ||
| { | ||
| "version": "3.9.0", | ||
| "date": "2026-04-04", | ||
| "wasm": { | ||
| "targets": { | ||
| "hub": "buildGraph", | ||
| "mid": "node", | ||
| "leaf": "docs" | ||
| }, | ||
| "fnDeps": { | ||
| "depth1Ms": 26.9, | ||
| "depth3Ms": 26.9, | ||
| "depth5Ms": 26.9 | ||
| }, | ||
| "fnImpact": { | ||
| "depth1Ms": 4, | ||
| "depth3Ms": 4, | ||
| "depth5Ms": 3.9 | ||
| }, | ||
| "diffImpact": { | ||
| "latencyMs": 7.9, | ||
| "affectedFunctions": 0, | ||
| "affectedFiles": 0 | ||
| } | ||
| }, | ||
| "native": { | ||
| "targets": { | ||
| "hub": "buildGraph", | ||
| "mid": "node", | ||
| "leaf": "docs" | ||
| }, | ||
| "fnDeps": { | ||
| "depth1Ms": 27.4, | ||
| "depth3Ms": 27.5, | ||
| "depth5Ms": 27.5 | ||
| }, | ||
| "fnImpact": { | ||
| "depth1Ms": 4, | ||
| "depth3Ms": 4, | ||
| "depth5Ms": 4 | ||
| }, | ||
| "diffImpact": { | ||
| "latencyMs": 9.3, | ||
| "affectedFunctions": 0, | ||
| "affectedFiles": 0 | ||
| } | ||
| } | ||
| }, | ||
| { | ||
| "version": "3.7.0", | ||
| "date": "2026-04-01", | ||
|
|
@@ -934,4 +985,5 @@ Latencies are median over 5 runs. Hub target = most-connected node. | |
| } | ||
| } | ||
| } | ||
| ] | ||
| --> | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fnDepslatency jumped from ~9.7ms (3.7.0) to ~27ms (3.9.0) — a ~180% increase — for both the native and WASM engines. This is the same order of magnitude as the regressions in 3.3.1→3.4.0 (↑136-143%) and 3.4.0→3.3.1 (↑157-192%), both of which have explanatory notes in the<!-- NOTES_START -->section documenting the cause (target changes, codebase growth, etc.).Without a corresponding note, it is unclear whether this is:
Please add an explanatory note to the
<!-- NOTES_START -->block for 3.9.0, following the same pattern as existing notes (e.g. the 3.4.0 note).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a Note (3.9.0) to the
<!-- NOTES_START -->block in commit 6fa6e54. The note explains:findCallersBatchrefactor in 3.8.1 (PR fix: v3.8.1 regression fixes (fnDeps, WASM lazy-load, edge parity, CI guard) #815)