Skip to content
Perf Canary

fix(extractors): resolve inline object-literal dispatch tables on WASM #466

Sign in to view logs

fix(extractors): resolve inline object-literal dispatch tables on WASM

fix(extractors): resolve inline object-literal dispatch tables on WASM #466

Triggered via pull request July 11, 2026 07:09
@carlos-almcarlos-alm
synchronize #2035
fix/issue-1897-engine-parity-wasm-doesnt-resolve-inline
Status Success
Total duration 11m 22s
Artifacts 1

perf-canary.yml

on: pull_request
Perf canary (incremental tiers)
11m 19s
Perf canary (incremental tiers)
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Benchmark Regression
[resolve] JS fallback: 9.7 → 11.6 (+20%, threshold 15%)
Benchmark Regression
[wasm] 1-file rebuild: 113 → 211 (+87%, threshold 15%)
Benchmark Regression
[wasm] No-op rebuild: 23 → 27 (+17%, threshold 15%)
Benchmark Regression
[wasm] Full build: 12219 → 15033 (+23%, threshold 15%)
Benchmark Regression
[native] 1-file rebuild: 117 → 191 (+63%, threshold 15%)
Benchmark Regression
[native] No-op rebuild: 24 → 29 (+21%, threshold 15%)
Benchmark Regression
[native] Full build: 3521 → 4680 (+33%, threshold 15%)

Artifacts

Produced during runtime
Name Size Digest
incremental-canary-result
623 Bytes
sha256:0854ad81986ab83217f4792afe5b40cb84d28ed484a32e771aa3219e92915db5