Skip to content

docs: update query benchmarks (3.9.6) #1031

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
carlos-alm merged 2 commits into from
Apr 30, 2026
Merged

docs: update query benchmarks (3.9.6) #1031

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
457489d
docs: update query benchmarks (3.9.6)
github-actions[bot] Apr 30, 2026
105d87b
Merge branch 'main' into benchmark/query-v3.9.6-20260430-065114
carlos-alm Apr 30, 2026
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
84 changes: 67 additions & 17 deletions generated/benchmarks/QUERY-BENCHMARKS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.6 | native | 28.7 ↑7% | 29.1 ↑7% | 33.2 ↑22% | 5.3 ↑8% | 5.5 ↑8% | 5.4 ↑6% | 16.7ms ↑129% |
Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Version gap: 3.9.5 skipped in benchmark history

The table jumps from 3.9.4 directly to 3.9.6 — there is no 3.9.5 row. If 3.9.5 was released but benchmarks weren't collected (e.g., it was a hotfix), this is fine, but worth confirming so readers don't assume it was not released. Was 3.9.5 released? If so, was it intentionally excluded from benchmarks (e.g., patch-only release)?

Fix in Claude Code

| 3.9.6 | wasm | 38.4 ~ | 40 ↑4% | 38.4 ↓2% | 5 ~ | 5 ↓19% | 4.9 ↓20% | 11.5ms ↓20% |
Comment on lines +8 to +9
Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Mid benchmark target changed between versions

The mid target node changed from ctx (3.9.4) to dir (3.9.6) in both native and WASM runs. The fnImpact depth metrics in the summary table reflect traversal from the hub (buildGraph), so they remain comparable, but benchmark runs that specifically exercise the mid-connectivity node are now on a different function. If ctx was renamed or removed in 3.9.6 this is expected — a small annotation in the "Latest results" section noting the target change would help readers interpret the relative ↑/↓ indicators for those runs. Was ctx renamed to dir in 3.9.6, or did the most representative mid-connectivity node simply shift? If the latter, are comparisons between 3.9.4 and 3.9.6 still meaningful for the mid-target benchmarks?

Fix in Claude Code

| 3.9.4 | native | 26.9 ↑10% | 27.3 ↑13% | 27.3 ↑13% | 4.9 ↑11% | 5.1 ↑16% | 5.1 ↑16% | 7.3ms ↓15% |
| 3.9.4 | wasm | 37.8 ↑10% | 38.5 ↑12% | 39.2 ↑15% | 5.1 ↑19% | 6.2 ↑41% | 6.1 ↑42% | 14.3ms ↑35% |
| 3.9.3 | native | 24.5 ~ | 24.2 ~ | 24.1 ~ | 4.4 ↓2% | 4.4 ↓4% | 4.4 ↓2% | 8.6ms ↓10% |
Expand Down Expand Up @@ -53,37 +55,37 @@ Latencies are median over 5 runs. Hub target = most-connected node.

### Latest results

**Version:** 3.9.4 | **Date:** 2026-04-18
**Version:** 3.9.6 | **Date:** 2026-04-30

#### Native (Rust)

**Targets:** hub=`buildGraph`, mid=`ctx`, leaf=`docs`
**Targets:** hub=`buildGraph`, mid=`dir`, leaf=`docs`

| Metric | Value |
|--------|------:|
| fnDeps depth 1 | 26.9ms |
| fnDeps depth 3 | 27.3ms |
| fnDeps depth 5 | 27.3ms |
| fnImpact depth 1 | 4.9ms |
| fnImpact depth 3 | 5.1ms |
| fnImpact depth 5 | 5.1ms |
| diffImpact latency | 7.3ms |
| fnDeps depth 1 | 28.7ms |
| fnDeps depth 3 | 29.1ms |
| fnDeps depth 5 | 33.2ms |
| fnImpact depth 1 | 5.3ms |
| fnImpact depth 3 | 5.5ms |
| fnImpact depth 5 | 5.4ms |
| diffImpact latency | 16.7ms |
| diffImpact affected functions | 0 |
| diffImpact affected files | 0 |

#### WASM

**Targets:** hub=`buildGraph`, mid=`ctx`, leaf=`docs`
**Targets:** hub=`buildGraph`, mid=`dir`, leaf=`docs`

| Metric | Value |
|--------|------:|
| fnDeps depth 1 | 37.8ms |
| fnDeps depth 3 | 38.5ms |
| fnDeps depth 5 | 39.2ms |
| fnImpact depth 1 | 5.1ms |
| fnImpact depth 3 | 6.2ms |
| fnImpact depth 5 | 6.1ms |
| diffImpact latency | 14.3ms |
| fnDeps depth 1 | 38.4ms |
| fnDeps depth 3 | 40ms |
| fnDeps depth 5 | 38.4ms |
| fnImpact depth 1 | 5ms |
| fnImpact depth 3 | 5ms |
| fnImpact depth 5 | 4.9ms |
| diffImpact latency | 11.5ms |
| diffImpact affected functions | 0 |
| diffImpact affected files | 0 |

Expand All @@ -106,6 +108,54 @@ Latencies are median over 5 runs. Hub target = most-connected node.

<!-- QUERY_BENCHMARK_DATA
[
{
"version": "3.9.6",
"date": "2026-04-30",
"wasm": {
"targets": {
"hub": "buildGraph",
"mid": "dir",
"leaf": "docs"
},
"fnDeps": {
"depth1Ms": 38.4,
"depth3Ms": 40,
"depth5Ms": 38.4
},
"fnImpact": {
"depth1Ms": 5,
"depth3Ms": 5,
"depth5Ms": 4.9
},
"diffImpact": {
"latencyMs": 11.5,
"affectedFunctions": 0,
"affectedFiles": 0
}
},
"native": {
"targets": {
"hub": "buildGraph",
"mid": "dir",
"leaf": "docs"
},
"fnDeps": {
"depth1Ms": 28.7,
"depth3Ms": 29.1,
"depth5Ms": 33.2
},
"fnImpact": {
"depth1Ms": 5.3,
"depth3Ms": 5.5,
"depth5Ms": 5.4
},
"diffImpact": {
"latencyMs": 16.7,
"affectedFunctions": 0,
"affectedFiles": 0
}
}
},
{
"version": "3.9.4",
"date": "2026-04-18",
Expand Down
Loading