Author	SHA1	Message	Date
Viktor Vaczi	da299ed6f9	bench: JSPI vs asyncify A/B — harness + results ... Adds pcbnew-large-perf.spec.ts (PERF_LARGE-gated: repeated cold loads, vme-wren/jetson opens, rAF + distinct-glcanvas-frame FPS under throttle, wasm/JS heap checkpoints), fetchIntoMemfs + openAndWait/sampleMemory/ measureFpsDetailed perf-utils, dual 9.99+10.0 config seeding in pcbnew.html so foreign-branch builds boot wizard-free, and the full benchmark report + raw data under docs/features/async/migration-evidence/. Headlines: wasm 94 vs 113 MB raw (18.6 vs 36.7 MB gzip), post-link tail 1.6 s/49 MB vs 63 s/6.1 GB per build, cold load −40 %, 27.7 MB board open −45 %, real redraws +68 % at 4× throttle, boot heap −31 %. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016X9eh1s5sTx1o9Em9KBuwR	2026-08-14 11:53:06 +02:00
Viktor Vaczi	3e5791774b	test(perf): track-only runtime-perf E2E for eeschema + pcbnew ... Measures the current build's cold load, open+render, and pan/zoom FPS (1x/4x/6x CPU-throttle sweep) for both editors, writing tests/test-results/perf-*.json. Track-only: asserts only that the app booted and the document opened — no perf thresholds, so it never gates CI. Runs on a new Chromium `perf` Playwright project (CDP throttling; pcbnew needs V8 anyway) via `npm run test:perf`, and is wired into wasm-build.yml as a continue-on-error step so the numbers are captured/uploaded without flaking the gate. Reuses the existing fixtures, ready-signal, fs-inject, and board-ready helpers; FPS counter is cancel-able so a throttle sweep on one page doesn't accumulate rAF loops. .gitignore: ignore /benchmark-builds/ (disposable prebuilt-WASM + standalone harness bundle used to reproduce the native-vs-JS-EH comparison locally). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-01 14:43:54 +02:00