cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: publish Phase 9 requalification decisions and evidence
MariaDB persistence qualification / mariadb (push) Failing after 7s
Details

Browse Source
This commit is contained in:
cesnimda
2026-10-24 18:32:24 +02:00
parent 7092697cb3
commit 3727a723e8
22 changed files with 53642 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-9/p9-requal-01/PERFORMANCE.md
+16 -2
View File
@@ -1,6 +1,6 @@
# P9-REQUAL-01 performance protocol
Status: **source prepared; real workload not executed by fixture author**. Historical P9-05 and RD21 sustained fixtures remain unchanged. Their short SQLite observations are not evidence for this lane. Actual runner results must be added below after the exclusive run.
Status: **PASS on real MariaDB12.2.2 after the documented fixture/provider repairs**. Historical P9-05 and RD21 sustained fixtures remain unchanged. Their short SQLite observations are not evidence for this lane. Actual runner results must be added below after the exclusive run.
The only new executable source is in `performance/`. It extends `job-tracker-ui/playwright.mariadb.config.ts`, preserving the canonical disposable-schema guard, MariaDB provider/version and `reuseExistingServer: false` on both servers. The additional guard requires port `33308` and a prebuilt production static frontend. No production code, dependencies, SQLite database, mock database or mocked API response is introduced.
@@ -51,4 +51,18 @@ The dependency-free self-check exercises empty percentiles, exact percentile bou
## Actual results
Pending root runner execution and evidence reconciliation. No measured duration, latency, throughput, preservation or capacity outcome is claimed yet.
Actual exclusive workload: **2026-10-24 13:10:23.274–13:25:23.280UTC**, monotonic duration **900006.3119ms** (required900000). Both readers completed1691 attempts: **3382 total, zero failures**. All20 navigations passed; maximum observed readiness1686.51ms. Preflight passed and is excluded from workload counts.
| Endpoint | Attempts | p50ms | p95ms | p99ms | Maxms |
| --- | ---: | ---: | ---: | ---: | ---: |
| All readers |3382|23.84|33.24|41.67|162.16|
| Application stats |846|22.43|27.80|34.03|57.79|
| Board |846|23.20|32.73|37.26|67.44|
| Career Profile |846|28.56|38.70|46.45|50.73|
| Documents |844|23.09|31.26|39.36|162.16|
The20 workload telemetry samples observed minimum host free memory13024960512bytes (12.13GiB) and maximum sampled load-generator NodeRSS478834688bytes (456.65MiB). These are sampled host/load-generator measures, not server CPU attribution or proof of the true between-sample peak. Windows load averages are unsupported zeros. Chrome CDP/DOM/heap and full per-request measurements remain in the attachment. No capacity/SLA claim is made.
Independent SQL snapshots matched exactly for the250 unique application IDs, owned/deleted/global-tenant counts, complete canonical profile JSON/revision, Identity projection JSON and history count. Full API profile and Board membership checks also passed. This is equality of the stated selected invariants, not a whole-database byte comparison or power-loss test. Cleanup verified the generated schema absent.
Accepted evidence: .artifacts/p9-requal-01/performance/result.json, performance.json, performance-exit.json and retained trace/attachment. The wrapper explicitly sets the root performance.json reporter path. Earlier setup/preflight failures remain separately archived and contribute zero successful timed runs. The canonical API-vs-storage setup comparison follows StructuredCvProfileJson.SerializePersisted null-property omission; exact SQL before/after equality, full API comparison and CV null-as-inherit contracts remain intact.