문제 fix/r1103-release(15-02)는 초기 JS 기준선을 feature-shape-ceilings.json의 initialJavascript 한 곳에 두고, test:unit이 빌드와 대조하게 했다. 열 개 조치 브랜치를 합친 빌드는 그 브랜치 하나로 잰 기록(200,939 B, 25개)과 다르다(15-01이 떨어뜨린 파일 하나, 세션·업로드·생성기 변경). 그래서 feature-shape-growth 테스트가 "initialJavascript is stale"로 실패한다. 고른 방법 - 기록 절차(performance-evidence.md)대로 measure-feature-shape-growth.ts --initial-baseline --write로 다시 쓴다. - 결과: 202,927 B, 26개, 기능 하나 +768 B, context 하나 +233 B. 예산 204,800 B에 여유 1,873 B다. 위험·한계 - 여유가 작다. --with-create 기능 하나(+약 964 B)를 넣으면 약 900 B가 남는다. 검증 - tests/unit/feature-shape-growth.test.ts 통과(heavy lock, CHOKIDAR_USEPOLLING=1). Refs: docs/reviews/2026-11-03-maturity-review/15-performance.md 15-02 15-04
48 lines
2.5 KiB
JSON
48 lines
2.5 KiB
JSON
{
|
|
"schemaVersion": 1,
|
|
"baseline": "config/scale/feature-shape-growth.json",
|
|
"ceilings": {
|
|
"contextMaxFeatures": 200,
|
|
"appMaxContexts": 20
|
|
},
|
|
"summary": "The ceilings bound the count; they are not a verified capacity. The practical limit of one app is the initial JavaScript budget, then typecheck memory. 400 features were not measured (D-18 makes it optional).",
|
|
"axes": [
|
|
{
|
|
"axis": "Typecheck of one app",
|
|
"verified": "Linear, about 117k instantiations and 36 MB of tsc memory per feature, up to 100 features",
|
|
"condition": "Reference-shaped features, tsconfig.app.json, the host recorded in the baseline",
|
|
"notVerified": "200 features (one full context) and beyond; 4,000 (20 x 200) would need on the order of 150 GB by the same slope"
|
|
},
|
|
{
|
|
"axis": "Production build",
|
|
"verified": "Completes at 100 features in seconds",
|
|
"condition": "Same",
|
|
"notVerified": "Beyond 100"
|
|
},
|
|
{
|
|
"axis": "Initial JavaScript",
|
|
"verified": "15-01: only each feature's declaration (route table, messages, invalidation identities) loads at boot; its runtime half loads with its routes, and a copy adds no initial file. initialJavascript below is the current template build, what one more feature in an existing context adds (perFeatureGzipBytes) and what a new context adds (perContextGzipBytes); tests/unit/feature-shape-growth.test.ts measures them on every unit run, bounds a feature at 1 KiB and a context at 512 B, and fails when the record no longer matches the build. The 25- and 100-copy runs are in the baseline at its source commit (before 15-01: +3,922 B per copy)",
|
|
"condition": "Same; the feature-declarations and feature-platform chunk groups in vite.config.ts",
|
|
"notVerified": "How many more features fit: the initial budget (config/performance/budgets.json) minus initialJavascript.gzipBytes, divided by perFeatureGzipBytes (plus perContextGzipBytes per new context). The platform itself takes most of the budget"
|
|
},
|
|
{
|
|
"axis": "Lazy JavaScript",
|
|
"verified": "About 8.5 KB gzip and eight files per feature, every file far below the 120 KiB lazy-chunk budget",
|
|
"condition": "Same",
|
|
"notVerified": "Download cost of many lazy files"
|
|
},
|
|
{
|
|
"axis": "Routes",
|
|
"verified": "4 per feature, composed without conflict",
|
|
"condition": "Same",
|
|
"notVerified": "Router matching cost at runtime"
|
|
}
|
|
],
|
|
"initialJavascript": {
|
|
"gzipBytes": 202927,
|
|
"files": 26,
|
|
"perFeatureGzipBytes": 768,
|
|
"perContextGzipBytes": 233
|
|
}
|
|
}
|