chore: use custom node build - #82
5 benchmarks regressed
⚠️ Unknown Walltime execution environment detected
Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.
For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.
⚠️ Different runtime environments detected
Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.
⚡ 19 improved benchmarks
❌ 5 regressed benchmarks
✅ 168 untouched benchmarks
⏩ 34 skipped benchmarks1
Warning
Please fix the performance issues or acknowledge them on CodSpeed.
Performance Changes
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Memory | fibo 30 |
19 B | 65,624 B | -99.97% |
| ❌ | Memory | wait 1ms |
7 B | 10 B | -30% |
| ❌ | Simulation | wait 500ms |
12.1 ms | 17 ms | -29.01% |
| ❌ | Simulation | wait 1sec |
23 ms | 32.3 ms | -28.91% |
| ❌ | WallTime | fibo darwin |
8.2 ms | 11.4 ms | -27.97% |
| ⚡ | Memory | short body 3 |
25,960 B | 11 B | ×2,400 |
| ⚡ | Memory | one |
45.9 KB | 14.4 KB | ×3.2 |
| ⚡ | Memory | wait 500ms |
64.1 KB | 23 KB | ×2.8 |
| ⚡ | WallTime | test_iterative_fibo_100 |
696 ns | 372 ns | +87.1% |
| ⚡ | WallTime | test_iterative_fibo_10 |
408 ns | 228 ns | +78.95% |
| ⚡ | WallTime | switch 1 |
288 ns | 192 ns | +50% |
| ⚡ | WallTime | iterative fibo 20 |
924 ns | 648 ns | +42.59% |
| ⚡ | WallTime | switch 2 |
324 ns | 228 ns | +42.11% |
| ⚡ | WallTime | iterative fibo 15 |
888 ns | 636 ns | +39.62% |
| ⚡ | WallTime | test sync baz 10 |
312 ns | 228 ns | +36.84% |
| ⚡ | WallTime | switch 2 |
312 ns | 228 ns | +36.84% |
| ⚡ | WallTime | switch 1 |
276 ns | 204 ns | +35.29% |
| ⚡ | WallTime | test_recursive_cached_fibo_10 |
1,152 ns | 852 ns | +35.21% |
| ⚡ | WallTime | test sync baz 100 |
444 ns | 336 ns | +32.14% |
| ⚡ | Simulation | wait 500ms |
12.9 ms | 10 ms | +28.96% |
| ... | ... | ... | ... | ... | ... |
ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing custom-node-build (5bcdbaf) with main (bcd7e64)
Footnotes
-
34 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. ↩