Phase 19: measure graph scaling and guard capacity and contention behavior
This commit is contained in:
parent
1369e4d463
commit
6b85f28add
9 changed files with 639 additions and 3 deletions
|
|
@ -416,6 +416,14 @@ path bounds, post-rename sync errors and physical power-loss limits are explicit
|
|||
- Overload behavior is defined and does not cause unbounded work in the callback.
|
||||
- Significant performance regressions can be detected through repeatable tests.
|
||||
|
||||
Implemented: 24-case node/channel/rate/block matrix with separate compilation
|
||||
and warmed process timings, recorded machine/compiler baseline and opt-in
|
||||
regression budgets; maximum track/clip/note/automation/meter capacity checks and
|
||||
publication/GUI tests under CPU contention. Measurements justified skipping
|
||||
unused live-controller processing; exact output tests remain passing. See
|
||||
PERFORMANCE.md and performance-baseline.json for results, thresholds and overload
|
||||
policy. Arbitrary plugin costs and physical realtime/endurance are unqualified.
|
||||
|
||||
## Phase 20 — Release Engineering, Packaging, and Maintenance
|
||||
|
||||
**Goal:** Make the application straightforward to build, install, use, diagnose, and maintain.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue