Miguel de Benito Delgado 756541939a
🔧 Add renderer benchmark runner (#12756)
Add a CLI under frontend/performance/benches/render_wasm that builds the
renderer, runs seeded scenes (rects, plus, paths, masks) in headless
Chromium and saves per-case timings.

- build, run: prepare or reuse builds; measure cases with warmups,
  repetitions, deadlines
- ab: build and compare Cargo feature configurations
- compare, merge: median changes with bootstrap CIs between saved runs,
  guarded by scene, build and settings checks
- purge: delete managed builds, runs or comparisons
- GPU runs through `run-devenv --gpu`

Lint, format and pnpm scripts now cover performance/ and its tests.

AI-assisted-by: gpt-6.1-sol, deepseek-flash, muse-spark, glm-5.3, gpt6-astra, claude-5.5-sonnet, claude-haiku-5.5
2026-11-12 11:02:34 +01:00

34 lines
835 B
HTML

<!doctype html>
<html>
<head>
<meta charset="utf-8" />
<title>Renderer benchmarks</title>
<style>
/* The canvas is the page: kill the UA body margin (8px) that would
leave a gutter around the scene in screenshots. */
html,
body {
margin: 0;
padding: 0;
}
canvas {
display: block;
}
</style>
</head>
<body>
<!-- Same one-liner as frontend/resources/polyfills/dynamicImport.js:
the bench bundle is plain ESM and must not depend on app boot. -->
<script>
globalThis.dynamicImport = function (u) {
return import(u);
};
</script>
<script type="module">
import bridge from "/browser/browser.js";
window.__benchBridge = bridge;
window.__benchReady = true;
</script>
</body>
</html>