perf(graph): build prepared relationship indexes with FxHash maps - #833
1 benchmark regressed
⚠️ Different runtime environments detected
Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
⚡ 4 improved benchmarks
❌ 1 regressed benchmark
✅ 79 untouched benchmarks
⏩ 4 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Memory | extract |
326.9 KB | 527.5 KB | -38.02% |
| ⚡ | Simulation | index_construction[16384] |
278.3 ms | 186.5 ms | +49.2% |
| ⚡ | Simulation | index_construction[4096] |
63.5 ms | 43.2 ms | +47.12% |
| ⚡ | Simulation | swift_facts |
2.2 ms | 1.5 ms | +42.6% |
| ⚡ | Simulation | extract |
15 ms | 12.8 ms | +16.99% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing execute-plan/79dd0742-pr-3-fxhash-preparedrelationshipindex-construction (a9f280e) with execute-plan/79dd0742-pr-2-faster-filenode-eq-and-interned-string-hashing (03ccd35)
Footnotes
-
4 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩