A fast 2D and 3D game engine — TypeScript SDK, C++/WebAssembly core, visual editor. Ship one project to web, desktop, WeChat MiniGames, playable ads, and native Android / iOS.
TypeScript 2d-game-engine3d3d-game-engineandroidcppecsgame-editorgame-enginegamedeviostypescriptwebassemblywebglwebgpuwechat-minigame
ci(scale): the budgets run on every push, and the numbers are kept
esenginea81810e89b77
diff --git a/.github/workflows/build.yml b/.github/workflows/build.ymlindex 7e8d128cb..a439d53ab 100644--- a/.github/workflows/build.yml+++ b/.github/workflows/build.yml@@ -258,6 +258,47 @@ jobs:ESENGINE_WASM_DIR: ${{ github.workspace }}/build/wasm/webrun: node tools/perf-guard.mjs --check+ # The other half of the performance contract: ceilings on whole operations at a+ # size no example reaches. Its own job because it generates a 50,000-asset+ # project first, and because a measurement sharing a runner with a test suite is+ # measuring the test suite. See bench/scale/README.md.+ scale:+ name: Scale budgets (50k assets)+ runs-on: ubuntu-latest+ needs: build-emscripten+ timeout-minutes: 30++ steps:+ - uses: actions/checkout@v7++ - uses: ./.github/actions/setup++ - name: Download web wasm artifact+ uses: actions/download-artifact@v8+ with:+ name: wasm-web+ path: build/wasm/web/++ # The scale suite loads the SHIPPED bundle (`esengine/node`), not src — a+ # probe tree-shaking drops from dist is one the users' engine does not have.+ - name: Build SDK+ run: pnpm --filter ./sdk build++ - name: Generate the corpus and check the budgets+ env:+ ESENGINE_WASM_DIR: ${{ github.workspace }}/build/wasm/web+ run: node tools/perf-budget.mjs++ # Every run's numbers, kept whether it passed or failed: a budget says what is+ # allowed, and the report is the only record of where a cost actually sits.+ - name: Upload the scale report+ if: always()+ uses: actions/upload-artifact@v7+ with:+ name: scale-report+ path: build/scale-report.json+ if-no-files-found: warn+# Headless pixel verification: real scenes rendered by the editor's electron# host under xvfb (SwiftShader WebGL), asserted pixel-by-pixel.verify-render:diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 7ddd07b8e..d3a456796 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -12,6 +12,36 @@ Version numbers here track the **Estella release** — the engine + editor + SDKshipped together, matching the Git tags and GitHub Releases. The SDK is notpublished separately; it ships inside the editor.+## [Unreleased]++### Added++- **A 50,000-asset project, and a set of costs it has to stay under.** Every scale+ problem this engine has had was reported by someone whose project was big enough+ to notice — 36k assets where deleting 22 files took 52 seconds, a folder of 788+ sprites that decoded 26 megapixels to show twenty. Nothing in this repository+ was ever that big: the examples exist to teach, so they are small, and a cost+ that only appears at 50k assets was invisible here until a user met it.+ `node tools/stress-project.mjs` generates one — 50,000 assets, 10,000 sprites,+ 5,000 UI nodes with masks inside masks, 2,000 physics bodies, 500 skeletons,+ 3,000 prefab instances with overrides, a 256×256×4 tilemap, and one scene+ holding all of it. It is generated rather than committed because 100,000 files+ would sit in front of every clone to store bytes that are a pure function of one+ script; the same seed gives the same tree byte for byte, in about eight seconds.+ `pnpm run scale` measures seventeen costs against it and holds each to a+ declared ceiling: project scan, incremental re-scan, delete, Find Usages, scene+ open and save, prefab instantiate, per-frame update, and what a scene retains+ after twenty open/close cycles.++ The ceilings are the point. The performance snapshot that already existed+ answers "did this change make it worse", and can always be accepted with+ `--update` — so a feature that takes scene-open from 200ms to 900ms passes by+ rewriting the number it is compared against. A ceiling cannot be raised by the+ change that breaks it. Because milliseconds do not survive a two-core shared+ runner, every budget is denominated in a reference workload measured in the same+ run — parse, loop, or file-read, whichever matches the metric's shape — so the+ same number means the same thing on a laptop and in CI.+## [0.46.0] - 2026-08-07### Added