SQLite Performance Audit

Database performance benchmarks with trend analysis and competitive context.

7/5/2026

69 min read

On this page

Note

Competitive comparisons based on publicly available documentation as of June 2026. All SveltyCMS metrics self-measured via bun test tests/benchmarks/.

Important

Console-only by default. Use BENCHMARK_RECORD=1 to write results to this report.

BENCHMARK_RECORD=1 bun test tests/benchmarks/auth-performance.test.ts

The full matrix runner (bun run scripts/benchmark-matrix/index.ts --db=sqlite) always records.

📊 Latest Performance Audit

📝 Fix Overlays

Note

Phase notes and remediation entries appear here after matrix or surgical runs.

Note

Partial update — dimension rollups and issues reflect only tests invoked in this run.

✅ PASS (partial invocation) · 1/62 tests · 61 skipped · sqlite · standalone run

Dimension health

Dimension	Tests	Status	Worst Δ
Core	24	🟢	—
API	0	⚪	—
Scale	0	⚪	—
Resilience	0	⚪	—

Issues (action required)

Executive latency matrix

Scenario	Latency	Trend	Budget	Result
Scale Spectrum	3.398ms	⚪ established at 3.40ms (1 run)	< 5ms	🟢
Scale Spectrum	3.158ms	⚪ established at 3.16ms (1 run)	< 5ms	🟢
Scale Spectrum	3.755ms	⚪ established at 3.75ms (1 run)	< 5ms	🟢
Scale Spectrum	2.631ms	⚪ established at 2.63ms (1 run)	< 5ms	🟢
Scale Spectrum	2.775ms	⚪ established at 2.77ms (1 run)	< 5ms	🟢
Scale Spectrum	2.752ms	⚪ established at 2.75ms (1 run)	< 5ms	🟢
Scale Spectrum	2.950ms	⚪ established at 2.95ms (1 run)	< 5ms	🟢
Scale Spectrum	2.265ms	⚪ established at 2.27ms (1 run)	< 5ms	🟢
Scale Spectrum	4.036ms	⚪ established at 4.04ms (1 run)	< 5ms	🟢
Scale Spectrum	2.124ms	⚪ established at 2.12ms (1 run)	< 5ms	🟢
Scale Spectrum	2.422ms	⚪ established at 2.42ms (1 run)	< 5ms	🟢
Scale Spectrum	1.770ms	⚪ established at 1.77ms (1 run)	< 5ms	🟢
Scale Spectrum	5.109ms	⚪ established at 5.11ms (1 run)	< 5ms	🟢
Scale Spectrum	1.959ms	⚪ established at 1.96ms (1 run)	< 5ms	🟢
Scale Spectrum	2.322ms	⚪ established at 2.32ms (1 run)	< 5ms	🟢
Scale Spectrum	1.742ms	⚪ established at 1.74ms (1 run)	< 5ms	🟢
Scale Spectrum	4.526ms	⚪ established at 4.53ms (1 run)	< 5ms	🟢
Scale Spectrum	2.079ms	⚪ established at 2.08ms (1 run)	< 5ms	🟢
Scale Spectrum	2.175ms	⚪ established at 2.17ms (1 run)	< 5ms	🟢
Scale Spectrum	1.477ms	⚪ established at 1.48ms (1 run)	< 5ms	🟢
Scale Spectrum	4.877ms	⚪ established at 4.88ms (1 run)	< 5ms	🟢
Scale Spectrum	1.674ms	⚪ established at 1.67ms (1 run)	< 5ms	🟢
Scale Spectrum	1.990ms	⚪ established at 1.99ms (1 run)	< 5ms	🟢
Scale Spectrum	1.524ms	⚪ established at 1.52ms (1 run)	< 5ms	🟢

Historical pulse

Metric	Trend	Sparkline	Latest
api latency (HTTP: findById @ 8c (Cold)) (warm)	🟢	`▅▆█▆▁▁`	3.053ms
auth performance (Auth Validation @ 1c) (warm)	🟢	`▃▃▆█▁▁▁▁▁▁▁`	0.307ms
cold start phased (Cold Start (IDLE → HTTP READY)) (cold)	🟢	`██▂▅▁▁▁▂`	1402.841ms
database performance (FIND MANY (limit 50)) (warm)	🟢	`▁▁▂▇▃▆█▆▁▁▁▁`	0.089ms

📈 Latency trend chart (last 10 runs)

xychart-beta title "sqlite REST p95 (last 10 runs)" x-axis ["R1", "R2", "R3", "R4", "R5", "R6", "R7", "R8", "R9", "R10"] y-axis "Latency (ms)" line "p95" : [0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000, 0.000]

Current Run Summary (2026-09-02)

Run ID: 3fc0408c-63c7-46cb-9829-48b4682768e8 · Tests invoked: 1 · Metrics: 24 · DB: sqlite

Test	Metric	Avg (ms)	p95 (ms)	RPS	Trend	Detail
Scale Spectrum	findByIdRandom @ 1	3.398	5.991	2271	🟢	⚪ established at 3.40ms (1 run)
Scale Spectrum	listFilterSort @ 1	3.158	3.523	2444	🟢	⚪ established at 3.16ms (1 run)
Scale Spectrum	graphql @ 1	3.755	4.120	2047	🟢	⚪ established at 3.75ms (1 run)
Scale Spectrum	create @ 1	2.631	3.095	1474	🟢	⚪ established at 2.63ms (1 run)
Scale Spectrum	findByIdRandom @ 10	2.775	3.703	2797	🟢	⚪ established at 2.77ms (1 run)
Scale Spectrum	listFilterSort @ 10	2.752	3.120	2808	🟢	⚪ established at 2.75ms (1 run)
Scale Spectrum	graphql @ 10	2.950	4.586	2625	🟢	⚪ established at 2.95ms (1 run)
Scale Spectrum	create @ 10	2.265	2.518	1706	🟢	⚪ established at 2.27ms (1 run)
Scale Spectrum	findByIdRandom @ 100	4.036	7.312	1935	🟢	⚪ established at 4.04ms (1 run)
Scale Spectrum	listFilterSort @ 100	2.124	2.489	3632	🟢	⚪ established at 2.12ms (1 run)
Scale Spectrum	graphql @ 100	2.422	2.810	3188	🟢	⚪ established at 2.42ms (1 run)
Scale Spectrum	create @ 100	1.770	1.944	2191	🟢	⚪ established at 1.77ms (1 run)
Scale Spectrum	findByIdRandom @ 1000	5.109	9.073	1516	🟢	⚪ established at 5.11ms (1 run)
Scale Spectrum	listFilterSort @ 1000	1.959	2.170	3945	🟢	⚪ established at 1.96ms (1 run)
Scale Spectrum	graphql @ 1000	2.322	2.626	3322	🟢	⚪ established at 2.32ms (1 run)
Scale Spectrum	create @ 1000	1.742	3.390	2228	🟢	⚪ established at 1.74ms (1 run)
Scale Spectrum	findByIdRandom @ 5000	4.526	5.170	1694	🟢	⚪ established at 4.53ms (1 run)
Scale Spectrum	listFilterSort @ 5000	2.079	4.957	3729	🟢	⚪ established at 2.08ms (1 run)
Scale Spectrum	graphql @ 5000	2.175	2.604	3553	🟢	⚪ established at 2.17ms (1 run)
Scale Spectrum	create @ 5000	1.477	1.692	2614	🟢	⚪ established at 1.48ms (1 run)
Scale Spectrum	findByIdRandom @ 10000	4.877	9.314	1581	🟢	⚪ established at 4.88ms (1 run)
Scale Spectrum	listFilterSort @ 10000	1.674	1.959	4602	🟢	⚪ established at 1.67ms (1 run)
Scale Spectrum	graphql @ 10000	1.990	2.194	3873	🟢	⚪ established at 1.99ms (1 run)
Scale Spectrum	create @ 10000	1.524	1.717	2540	🟢	⚪ established at 1.52ms (1 run)

Historical Trends (2026-09-02)

Detail: tests/benchmarks/results/history.sqlite · SELECT test_id, phase, avg_ms, p95_ms, rps, timestamp FROM runs WHERE db_type='sqlite' AND redis=0 ORDER BY timestamp DESC

Series: 57 · DB: sqlite

Metric	Trend	Sparkline (last 7)	Latest
ADMIN UX VITALITY (warm)	🟢	`▁█▄█`	4.044ms
AI PERFORMANCE (warm)	🟢	`▁▁█▁`	0.001ms
API LATENCY (warm)	🟢	`▆█▄▂▁▃▁`	1.521ms
AUTH PERFORMANCE (warm)	🟢	`▂▁█▂▁█▂`	0.439ms
CACHE HIT RATIO (warm)	🟢	`█▄▇▁▂▁▂`	0.561ms
CACHE PERFORMANCE (warm)	🟢	`█▁▁▁▁▁▁`	0.319ms
CACHE SERVICE (warm)	🟢	`▁█▅▁▁▁▂`	0.857ms
CLIENT JOURNEY (warm)	🟢	`█▇▁▁`	2.187ms
COLD START PHASED (cold)	🟢	`█▂▅▁▁▁▂`	1402.841ms
COMPETITIVE WORKLOAD REPLICA (warm)	🟢	`▁▄▁█▂█▁`	0.534ms
CONCURRENCY MAX (warm)	🟢	`▁█▇`	835.712ms
CONFIG PROMOTION (warm)	🟢	`▁▄▅▄█▃▂`	4.627ms
CONTENT SCALE STRESS (warm)	🟢	`▇▁█▂▆▂`	0.706ms
CONTENT SCAN (warm)	🟢	`▃▁▇█▂▂`	4.486ms
DATA RESIDENCY FAILOVER (warm)	🟢	`▁▂▅█▄▅`	2.825ms
DATABASE PERFORMANCE (warm)	🟢	`▂▂▂▁█▁▁`	0.038ms
ENTRY EDIT HYDRATION (warm)	🟢	`▂▁▅█▂▁█`	0.058ms
FAILURE PROPAGATION (warm)	🟢	`▁▆█▅▇█▅`	2.855ms
GRAPHQL API PERFORMANCE (warm)	🟢	`▅▅▄█▅▁▁`	0.354ms
GRAPHQL CACHE HIT (warm)	🟢	`▁▃▁█▁▄▁`	0.538ms
GRAPHQL LOCAL SDK (warm)	🟢	`▁█▁█▁█▁`	0.000ms
GRAPHQL STRESS (warm)	🟢	`█▁▂▄▁▅▇`	17.461ms
HOOKS PERFORMANCE (warm)	🟢	`█▁▃▁█▁█`	0.597ms
INDEX PRESSURE (warm)	🟢	`▄█▁▅`	1.770ms
LARGE PAYLOAD STREAMING (warm)	🟢	`█▅▆▃▁▇▄`	16.614ms
LOCAL API PERFORMANCE (warm)	🟢	`▁▁▁▁█▁▁`	0.008ms
LOCAL API THROUGHPUT (warm)	🟢	`▇█▇▁▂▁▁`	0.334ms
LOCAL CMS CRUD (warm)	🟢	`▆▁▅▁▁█▄`	0.057ms
LOCAL SDK VS DIRECT (warm)	🟢	`▄▆▄█▁▄▄`	0.149ms
LONGEVITY SOAK (warm)	🟢	`█▃▆█▃▆▁`	0.670ms
MEDIA PERFORMANCE (warm)	🟢	`█▁▅▄▁▄▄`	109.651ms
MEDIA UPLOAD STRESS (warm)	🟢	`▁▂▄█▄▄`	170.481ms
MEMORY STABILITY (warm)	🟢	`▁▁`	0.000ms
MIGRATION SCALE (warm)	🟢	`▁▄▁▁█▁▁`	4.044ms
MIXED WORKLOAD (warm)	🟢	`▂█▃▁`	2.094ms
MULTI TENANT PERFORMANCE (warm)	🟢	`▁██`	6.059ms
NEGATIVE CACHE (warm)	🟢	`▁██▁▇▇▁`	0.001ms
OPENAPI PERFORMANCE (warm)	🟢	`▁▄▆▂▇█▂`	0.656ms
PRODUCTION DAY (warm)	🟢	`▁▇█`	6.238ms
REALTIME PERFORMANCE (warm)	🟢	`▁▁█▁▁█▁`	0.000ms
RELATIONAL PERFORMANCE (warm)	🟢	`█▃▁▂▃▁▂`	2.207ms
REST API PERFORMANCE (warm)	🟢	`▃▁█▇▇█▄`	0.786ms
REVISION STRESS (warm)	🟢	`▄█▃▇▃▁▂`	0.740ms
RIGHT TO BE FORGOTTEN AUDIT (warm)	🟢	`▁▁▁█▆`	2.485ms
SCALE SPECTRUM (warm)	🟢	`▃█▆▃▂▁▃`	2.079ms
SECURITY AUDIT (warm)	🟢	`▁█▁▁▁▁▁`	0.002ms
SEO PERFORMANCE (warm)	🟢	`█▁▁▁█▁▁`	6.715ms
STATE MACHINE TRANSITION (warm)	🟢	`█▇▇▁▁▂▄`	30.898ms
TELEMETRY PERFORMANCE (warm)	🟢	`█▁▃▁`	0.001ms
TEMPORAL INTEGRITY (warm)	🟢	`▄▁▁▆▄▄█`	2.797ms
TRANSACTION ACID (warm)	🟢	`█▁▃▁▃▁▃`	0.109ms
TRUTH LATENCY (warm)	🟢	`▇▁▁█▇▁▁`	0.000ms
WEBSOCKET BROADCAST (warm)	🟢	`▁▁▁█▆`	0.497ms
WIDGET PERFORMANCE (warm)	🟢	`▃▇▁█▇▁█`	0.123ms
CONTENT INCREMENTAL RELOAD (warm)	⚪	`▁▁█▄▂▁█`	8.829ms
MIDDLEWARE FLAMEGRAPH (warm)	⚪	`▃▂▁▃▂▂█`	3.376ms
THROTTLING BACKOFF STRESS (warm)	⚪	`▃▁▃▂█▂▇`	31.860ms

🔬 Full benchmark ledger (58 modules)

Expand dimension groups, then any row, for ASCII truth tables. Executive summary above shows pass/fail and issues only.

Core · 84 tests

🏷️ API LAYER LATENCY · 🟢 4.660ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                     SVELTYCMS — API LAYER LATENCY                                     ║
║                              File: tests/benchmarks/api-latency.test.ts                               ║
║                                       Ran: 2026-09-02 18:32:00                                        ║
║              Cold full-pipeline findById + warm TURBO-HIT path after responseCache fill.              ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ HTTP: findById @ 8c (Cold)   │ Cold:     4.66 ms │ Warm:     3.053 ms │ p95:     4.864 ms │   2,517 RPS ║
║ HTTP: findById TURBO-HIT @ 8c (Warm) │ Cold:     0.45 ms │ Warm:     1.521 ms │ p95:     1.869 ms │   5,044 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ cold start phased · 🟢 1402.841ms · ➡️ ⚪ stable at 1382.11ms (±713.22ms) (7 runs) (2026-09-02 19:38:51) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — PHASED COLD START AUDIT ║ ║ File: tests/benchmarks/cold-start-phased.test.ts ║ ║ Ran: 2026-09-02 19:38:51 ║ ║ Measures process spawn, dependency hydration, and first-request TTFB readiness. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Initial Cold Boot (Fresh Process) │ 1920.263 ms │ p95: 1920.263 ms │ RPS: 0 ║ ║ Steady-State Respawn (Average) │ 1402.841 ms │ p95: 1920.263 ms │ RPS: 0 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ SRE TRUTH AUDIT · 🟢 0.010ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                      SVELTYCMS — SRE TRUTH AUDIT                                      ║
║                             File: tests/benchmarks/truth-latency.test.ts                              ║
║                                       Ran: 2026-09-02 19:38:59                                        ║
║            Validates performance claims by comparing SDK, Middleware, and Real HTTP Stack             ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Logic Baseline               │ Cold:     0.01 ms │ Warm:     0.000 ms │ p95:     0.000 ms │ 528,355 RPS ║
║ Local SDK (Full)             │ Cold:     1.96 ms │ Warm:     0.004 ms │ p95:     0.007 ms │ 207,929 RPS ║
║ HTTP End-to-End              │ Cold:     4.20 ms │ Warm:     0.422 ms │ p95:     0.493 ms │   2,357 RPS ║
║ HTTP Cold (Cache-Busted)     │ Cold:     1.23 ms │ Warm:     0.523 ms │ p95:     0.976 ms │   1,905 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Self-Healing Content Scan · 🟢 3.142ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                    SVELTYCMS — CONTENT SCAN AUDIT                                     ║
║                              File: tests/benchmarks/content-scan.test.ts                              ║
║                                       Ran: 2026-08-29 21:34:18                                        ║
║          Measures filesystem + metadata processing and persistent Mtime dirty-bit discovery.          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Cold Discovery (Filesystem I/O) │        3.142 ms │ p95:        3.645 ms │ RPS:        318 ║
║ Warm Discovery (Mtime Tree Hit) │ Cold:     1.94 ms │ Warm:     1.666 ms │ p95:     2.906 ms │     552 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Incremental Content Reload · 🟢 3.270ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                             SVELTYCMS — INCREMENTAL CONTENT RELOAD AUDIT                              ║
║                       File: tests/benchmarks/content-incremental-reload.test.ts                       ║
║                                       Ran: 2026-08-29 21:34:19                                        ║
║      Measures surgical single-file fullReload vs full reconciliation path and batch processing.       ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Incremental fullReload (1 file) │ Cold:     3.27 ms │ Warm:     0.198 ms │ p95:     0.518 ms │   3,732 RPS ║
║ Full Reconciliation Reload   │ Cold:     2.84 ms │ Warm:     0.292 ms │ p95:     0.465 ms │   3,097 RPS ║
║ Sequential 10-File Reload    │ Cold:     5.53 ms │ Warm:     2.696 ms │ p95:     4.671 ms │     370 RPS ║
║ Batched 10-File Reload       │ Cold:     1.79 ms │ Warm:     1.076 ms │ p95:     1.194 ms │     918 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Middleware & Hooks Performance · 🟢 2.370ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — MIDDLEWARE & HOOKS AUDIT                                  ║
║                           File: tests/benchmarks/hooks-performance.test.ts                            ║
║                                       Ran: 2026-09-02 22:14:42                                        ║
║Measures the cost of the full middleware chain including Turbo, Security, Auth, and Audit via HTTP E2E.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Static Asset (No Middleware) │ Cold:     2.37 ms │ Warm:     0.552 ms │ p95:     0.638 ms │   1,792 RPS ║
║ Turbo Pipeline (Light)       │ Cold:     1.16 ms │ Warm:     0.279 ms │ p95:     0.366 ms │   3,463 RPS ║
║ Full Security + Auth Pipeline │ Cold:     4.02 ms │ Warm:     0.352 ms │ p95:     0.469 ms │   2,749 RPS ║
║ REST with API Caching        │ Cold:     3.20 ms │ Warm:     0.310 ms │ p95:     0.401 ms │   3,168 RPS ║
║ Mutation (audit logging disabled) │ Cold:     4.27 ms │ Warm:     0.581 ms │ p95:     0.677 ms │   1,711 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Edge Sync & Distributed Cache · 🟢 14.050ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                SVELTYCMS — EDGE SYNC PROPAGATION AUDIT                                ║
║                               File: tests/benchmarks/edge-sync.test.ts                                ║
║                                       Ran: 2026-08-29 21:35:27                                        ║
║    Measures cache invalidation propagation latency across real edge nodes via live Redis Pub/Sub.     ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Edge Sync Propagation        │ Cold:    14.05 ms │ Warm:    15.529 ms │ p95:    16.135 ms │      67 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Telemetry · 🟢 0.150ms · ➡️ recorded (awaiting trend) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — TELEMETRY & UPDATE PERFORMANCE ║ ║ File: tests/benchmarks/telemetry-performance.test.ts ║ ║ Ran: 2026-08-29 21:32:18 ║ ║Measures telemetry update check latency and memory impact on both happy-path and failure-path scenarios.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Telemetry (Happy Path) │ Cold: 0.15 ms │ Warm: 0.000 ms │ p95: 0.001 ms │ 778,059 RPS ║ ║ Telemetry (Failure Path) │ Cold: 0.04 ms │ Warm: 0.001 ms │ p95: 0.002 ms │ 777,907 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ State Machine Transitions · 🟢 37.120ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — STATE MACHINE INTEGRITY                                  ║
║                        File: tests/benchmarks/state-machine-transition.test.ts                        ║
║                                       Ran: 2026-08-29 21:34:25                                        ║
║Measures state machine self-healing transition latencies, convergence settling time, and health probe consistency under stress.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ State Transition (Transient) │ Cold:    37.12 ms │ Warm:    18.969 ms │ p95:    20.386 ms │      52 RPS ║
║ Self-Healing Full Convergence │ Cold:    23.80 ms │ Warm:    18.759 ms │ p95:    19.707 ms │      53 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ database performance · 🟢 0.784ms · ↘️ ⚪ stable at 1.33ms (±2.11ms) (7 runs) (2026-09-02 19:40:04) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                           SVELTYCMS — DATABASE ADAPTER PERFORMANCE (SQLITE)                           ║
║                          File: tests/benchmarks/database-performance.test.ts                          ║
║                                       Ran: 2026-09-02 19:40:04                                        ║
║          Measures raw CRUD performance, indexing efficiency, and connection pool resilience.          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ INSERT                       │ Cold:     0.47 ms │ Warm:     0.070 ms │ p95:     0.162 ms │   5,752 RPS ║
║ FIND ONE                     │ Cold:     0.31 ms │ Warm:     0.006 ms │ p95:     0.009 ms │ 152,896 RPS ║
║ FIND MANY (limit 50)         │ Cold:     1.14 ms │ Warm:     0.089 ms │ p95:     0.118 ms │   8,947 RPS ║
║ QUERY BUILDER LIST (50)      │ Cold:     3.15 ms │ Warm:     0.791 ms │ p95:     0.944 ms │   1,162 RPS ║
║ FIND PAGE (50 hasMore)       │ Cold:     1.39 ms │ Warm:     0.110 ms │ p95:     0.149 ms │   7,523 RPS ║
║ FIND PAGE keyset             │ Cold:     2.32 ms │ Warm:     0.111 ms │ p95:     0.154 ms │   7,477 RPS ║
║ FIND MANY offset 50          │ Cold:     0.62 ms │ Warm:     0.054 ms │ p95:     0.069 ms │  15,257 RPS ║
║ LIST+COUNT (legacy)          │ Cold:     1.12 ms │ Warm:     0.152 ms │ p95:     0.236 ms │   5,431 RPS ║
║ UPDATE                       │ Cold:     2.26 ms │ Warm:     0.043 ms │ p95:     0.085 ms │  10,763 RPS ║
║ UPDATE (no-returning)        │ Cold:     0.76 ms │ Warm:     0.038 ms │ p95:     0.073 ms │  11,103 RPS ║
║ NATIVE UPSERT                │ Cold:     1.46 ms │ Warm:     0.083 ms │ p95:     0.136 ms │   6,821 RPS ║
║ COUNT                        │ Cold:     1.09 ms │ Warm:     0.063 ms │ p95:     0.085 ms │  13,865 RPS ║
║ COUNT ESTIMATE               │ Cold:     0.65 ms │ Warm:     0.019 ms │ p95:     0.027 ms │  45,485 RPS ║
║ COUNT CACHED                 │ Cold:     3.92 ms │ Warm:     0.001 ms │ p95:     0.003 ms │ 467,072 RPS ║
║ DELETE (Active Rows)         │ Cold:     5.41 ms │ Warm:     0.055 ms │ p95:     0.088 ms │   7,241 RPS ║
║ BULK INSERT (100)            │ Cold:     1.82 ms │ Warm:    14.820 ms │ p95:    41.431 ms │      67 RPS ║
║ BULK UPDATE (100 heterogeneous) │ Cold:    11.64 ms │ Warm:     1.294 ms │ p95:     9.767 ms │     434 RPS ║
║ BULK UPDATE (100 homogeneous) │ Cold:    25.66 ms │ Warm:     0.784 ms │ p95:     1.705 ms │   1,050 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ transaction acid · 🟢 0.109ms · ↘️ ⚪ stable at 0.220ms (±0.223ms) (7 runs) (2026-09-02 19:40:15) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — ACID INTEGRITY AUDIT                                    ║
║                            File: tests/benchmarks/transaction-acid.test.ts                            ║
║                                       Ran: 2026-09-02 19:40:15                                        ║
║         Measures transaction commit latencies and rollback overhead across database adapters          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ TX Commit                    │ Cold:     0.42 ms │ Warm:     0.005 ms │ p95:     0.020 ms │ 194,941 RPS ║
║ TX Rollback Integrity        │ Cold:     0.89 ms │ Warm:     0.109 ms │ p95:     0.141 ms │   9,046 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Cache · 🟢 0.298ms · ↘️ ⚪ stable at 0.614ms (±0.804ms) (5 runs) (2026-09-02 19:40:25) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — CACHE EFFICIENCY AUDIT                                   ║
║                           File: tests/benchmarks/cache-performance.test.ts                            ║
║                                       Ran: 2026-09-02 19:40:25                                        ║
║         Measures cache hit vs miss latency and efficiency via real HTTP end-to-end requests.          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Cache Miss (Bypass)          │ Cold:     1.23 ms │ Warm:     0.319 ms │ p95:     0.488 ms │   2,793 RPS ║
║ Cache Hit (L1 Warm)          │ Cold:     2.31 ms │ Warm:     0.298 ms │ p95:     0.477 ms │   2,906 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ cache hit ratio · 🟢 0.684ms · ➡️ recorded (awaiting trend) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — CACHE EFFICIENCY AUDIT ║ ║ File: tests/benchmarks/cache-hit-ratio.test.ts ║ ║ Ran: 2026-09-02 15:32:10 ║ ║ Measures true cold-fill, warm hit ratio, miss penalty, and invalidation latency. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Cache Cold Fill (Miss + Repopulate) │ 0.684 ms │ p95: 1.438 ms │ RPS: 1,463 ║ ║ Cache Hit (Warm) │ Cold: 0.57 ms │ Warm: 0.337 ms │ p95: 0.526 ms │ 2,709 RPS ║ ║ Bypass Cache (Direct DB) │ Cold: 1.31 ms │ Warm: 0.354 ms │ p95: 0.414 ms │ 2,802 RPS ║ ║ Cache Invalidation │ Cold: 1.15 ms │ Warm: 0.561 ms │ p95: 0.685 ms │ 1,614 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Production Build Analysis · ⚪ ⏳ pending · ➡️ pending · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — PRODUCTION BUILD ANALYSIS                                 ║
║                             File: tests/benchmarks/build-analysis.test.ts                             ║
║                                       Ran: 2026-08-29 21:35:30                                        ║
║              Measures compilation speed, bundle size trends, and tree-shaking efficiency              ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Production Build               │        0.000 ms │ p95:        0.000 ms │ RPS:          0 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ DX Toolchain Performance · ⏳ pending · ➡️ baseline · source

🏷️ CacheService Micro-Benchmark · 🟢 4.111ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — CACHE SERVICE TELEMETRY                                  ║
║                             File: tests/benchmarks/cache-service.test.ts                              ║
║                                       Ran: 2026-08-29 21:34:13                                        ║
║               Measures L1 cache hit latency and pattern invalidation overhead at scale.               ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Cache L1 Hit                 │ Cold:     0.25 ms │ Warm:     0.000 ms │ p95:     0.001 ms │ 1,392,147 RPS ║
║ Pattern Invalidation (1k items @ 200k noise) │        4.111 ms │ p95:        5.134 ms │ RPS:        243 ║
║ Pattern Invalidation (Namespaced 1k @ 100k noise) │        1.894 ms │ p95:        2.307 ms │ RPS:        528 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ LocalCMS SDK Overhead · 🟢 0.598ms · ➡️ recorded (awaiting trend) · source

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                     SVELTYCMS — DIRECT ADAPTER THROUGHPUT (SQLITE)                      ║
║                   File: tests/benchmarks/local-api-throughput.test.ts                   ║
║                                Ran: 2026-08-28 10:17:19                                 ║
║Measures direct adapter write throughput, read throughput, and percentile latencies with zero HTTP overhead.║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ Writes (1000 atomic increments) │        0.598 ms │ p95:        0.588 ms │ RPS:      9,965 ║
║ Reads (1000 point lookups)     │        0.573 ms │ p95:        1.451 ms │ RPS:     76,610 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Setup Proxy & Bootstrap Isolation · ⏳ pending · ➡️ baseline · source

🏷️ HTTP · 🟢 0.422ms · ↘️ ⚪ stable at 0.463ms (±0.244ms) (7 runs) (2026-09-02 19:39:10) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Logic · 🟢 ⏳ pending · ➡️ ⚪ stable at 0ms (±0.001ms) (7 runs) (2026-09-02 19:39:10) · source

> ⏳ Pending

🏷️ SDK · 🟢 0.004ms · ➡️ ⚪ stable at 0.004ms (±0.029ms) (7 runs) (2026-09-02 19:39:10) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — SDK VS DIRECT ADAPTER (SQLITE) ║ ║ File: tests/benchmarks/local-sdk-vs-direct.test.ts ║ ║ Ran: 2026-08-31 09:11:35 ║ ║Measures the exact SDK tax across Create, Find, and Update pathways with isolated GC sweeps and zero-allocation key pools.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Direct insert │ 0.171 ms │ p95: 0.171 ms │ RPS: 5,841 ║ ║ SDK create (full) │ 0.256 ms │ p95: 0.256 ms │ RPS: 3,912 ║ ║ Direct findOne │ 0.018 ms │ p95: 0.018 ms │ RPS: 55,545 ║ ║ SDK find (bypassCache) │ 0.012 ms │ p95: 0.012 ms │ RPS: 85,479 ║ ║ Direct update │ 0.134 ms │ p95: 0.134 ms │ RPS: 7,483 ║ ║ SDK update (full) │ 0.149 ms │ p95: 0.149 ms │ RPS: 6,722 ║ ║ SDK create (detached) │ 0.337 ms │ p95: 0.337 ms │ RPS: 2,971 ║ ║ SDK update (detached) │ 0.144 ms │ p95: 0.144 ms │ RPS: 6,952 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ unknown · 🟢 0.002ms · ➡️ recorded (awaiting trend) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 95% — check connection pool saturation or lock contention. **Severe degradation** (+2182%) — review recent commits immediately.

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                      SVELTYCMS — CACHE EVICTION BOUNDARY HARDENING                      ║
║                                      File: unknown                                      ║
║                                Ran: 2026-08-23 22:49:42                                 ║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ Cache Flooding & Eviction      │        0.002 ms │ p95:        0.002 ms │ RPS:    491,908 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Middleware · 🟢 0.597ms · ↘️ ⚪ stable at 0.743ms (±1.34ms) (7 runs) (2026-09-02 19:40:36) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                         MIDDLEWARE FLAMEGRAPH PROFILER (SQLITE)                         ║
║                  File: tests/benchmarks/middleware-flamegraph.test.ts                   ║
║                                Ran: 2026-08-28 10:30:57                                 ║
║Measures isolated microsecond cost and incremental deltas of each middleware stage from edge to database.║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ Stage 0: Raw Socket Baseline (Static Asset) │        1.227 ms │ p95:        2.512 ms │ RPS:      2,954 ║
║ Stage 1: System State + Turbo Pipeline │        0.991 ms │ p95:        2.425 ms │ RPS:      3,157 ║
║ Stage 2: WAF Security Inspection │        0.578 ms │ p95:        1.756 ms │ RPS:      5,732 ║
║ Stage 3: Token Auth Gating     │        1.196 ms │ p95:        2.409 ms │ RPS:      3,008 ║
║ Stage 4: Collection Schema Resolution │        1.134 ms │ p95:        2.318 ms │ RPS:      3,164 ║
║ Stage 5: Full REST Single Document │        1.014 ms │ p95:        2.179 ms │ RPS:      3,485 ║
║ Stage 6: GraphQL Single Query (JIT) │        3.376 ms │ p95:        5.097 ms │ RPS:      1,148 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ System · 🟢 0.786ms · ↗️ ⚪ stable at 0.691ms (±1.18ms) (6 runs) (2026-09-02 19:40:47) · source

> [!NOTE] > **Specific to this test**: Avg degraded but p95 stable — possible cold-start effect, GC pause, or warmup variance.

🏷️ Metadata · 🟢 0.900ms · ↘️ ⚪ stable at 0.990ms (±1.13ms) (6 runs) (2026-09-02 19:40:47) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ CRUD · 🟢 0.515ms · ➡️ ⚪ established at 0.515ms (1 run) (2026-08-25 11:26:43) · source

> ⏳ Pending

🏷️ Crypto · ⚪ 4.983ms · ↗️ 🔴 slower: 0.749ms → 4.98ms (+565%) (7 runs) (2026-08-29 13:05:52) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 85% — check connection pool saturation or lock contention. **Severe degradation** (+565%) — review recent commits immediately.

🏷️ Defense · 🟢 ⏳ pending · ➡️ ⚪ stable at 0ms (7 runs) (2026-08-23 16:33:40) · source

> ⏳ Pending

🏷️ L1 · 🟢 4.015ms · ➡️ ⚪ established at 4.01ms (1 run) (2026-08-11 23:02:18) · source

> ⏳ Pending

🏷️ DB · 🟢 0.134ms · ➡️ ⚪ established at 0.134ms (1 run) (2026-08-31 09:11:35) · source

> ⏳ Pending

🏷️ TURBO · 🟢 1.521ms · ↘️ ⚪ stable at 4.74ms (±2.44ms) (5 runs) (2026-09-02 18:32:00) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Stress · 🟢 20.136ms · ↘️ ⚪ stable at 58.86ms (±68.22ms) (7 runs) (2026-09-02 18:21:18) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — REVISION STRESS AUDIT                                   ║
║                            File: tests/benchmarks/revision-stress.test.ts                             ║
║                                       Ran: 2026-08-29 21:33:01                                        ║
║Measures latest read degradation, history retrieval speed, and storage footprint under heavy revision growth (100 revisions).║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Clean Document Read (Baseline) │ Cold:     1.70 ms │ Warm:     1.217 ms │ p95:     2.091 ms │   3,099 RPS ║
║ Latest Read (100 Revisions)  │ Cold:     1.52 ms │ Warm:     1.171 ms │ p95:     2.263 ms │   3,094 RPS ║
║ History List Retrieval       │ Cold:     5.34 ms │ Warm:     0.599 ms │ p95:     1.053 ms │   3,010 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Client · 🟢 ⏳ pending · ➡️ ⚪ established at 0ms (1 run) (2026-08-23 15:48:15) · source

> ⏳ Pending

🏷️ GraphQL (cold) · 🟢 2.611ms · ↘️ ⚪ stable at 2.81ms (±6.95ms) (7 runs) (2026-09-02 18:21:03) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ GraphQL (hot) · 🟢 1.628ms · ↘️ ⚪ stable at 1.72ms (±5.19ms) (7 runs) (2026-09-02 18:21:04) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Content · 🟢 4.714ms · ↗️ ⚪ stable at 1.16ms (±2.98ms) (3 runs) (2026-08-29 12:58:02) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 53% — check connection pool saturation or lock contention. **Severe degradation** (+305%) — review recent commits immediately.

🏷️ Analytics · 🟢 55.434ms · ↗️ ⚪ stable at 15.13ms (±53.44ms) (3 runs) (2026-08-29 12:58:02) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 82% — check connection pool saturation or lock contention. **Severe degradation** (+266%) — review recent commits immediately.

🏷️ Status · 🟢 4.627ms · ➡️ ⚪ established at 4.63ms (1 run) (2026-08-28 09:35:03) · source

> ⏳ Pending

🏷️ 10 collections · 🟢 8.165ms · ➡️ ⚪ established at 8.16ms (1 run) (2026-08-28 09:35:03) · source

> ⏳ Pending

🏷️ 50 collections · 🟢 8.746ms · ➡️ ⚪ established at 8.75ms (1 run) (2026-08-28 09:35:03) · source

> ⏳ Pending

🏷️ 100 collections · 🟢 11.605ms · ➡️ ⚪ established at 11.61ms (1 run) (2026-08-28 09:35:03) · source

> ⏳ Pending

🏷️ Planning · 🟢 6.756ms · ➡️ ⚪ established at 6.76ms (1 run) (2026-08-28 09:35:03) · source

> ⏳ Pending

🏷️ Apply · 🟢 17.580ms · ➡️ ⚪ established at 17.58ms (1 run) (2026-08-28 09:35:03) · source

> ⏳ Pending

🏷️ Cache (Miss) · 🟢 0.684ms · ↘️ ⚪ stable at 2.55ms (±1.31ms) (3 runs) (2026-09-02 15:32:10) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Cache (Hit) · ⚪ 0.337ms · ↘️ 🟢 faster: 1.24ms → 0.337ms (-73%) (3 runs) (2026-09-02 15:32:10) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Database · ⚪ 0.354ms · ↘️ 🟢 faster: 1.49ms → 0.354ms (-76%) (3 runs) (2026-09-02 15:32:10) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Mutation · ⚪ 0.561ms · ↘️ 🟢 faster: 2.10ms → 0.561ms (-73%) (3 runs) (2026-09-02 15:32:10) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Auth · 🟢 1.378ms · ➡️ ⚪ stable at 1.45ms (±0.178ms) (7 runs) (2026-09-02 19:57:33) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — AUTHENTICATION TELEMETRY ║ ║ File: tests/benchmarks/auth-performance.test.ts ║ ║ Ran: 2026-09-02 19:57:33 ║ ║ Evaluates authenticated session resolution, RBAC evaluation, and rejection paths. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Unauthenticated (401 Fast Path) │ Cold: 1.41 ms │ Warm: 0.439 ms │ p95: 0.584 ms │ 2,116 RPS ║ ║ Auth Validation @ 1c │ Cold: 1.64 ms │ Warm: 0.307 ms │ p95: 0.390 ms │ 3,186 RPS ║ ║ HTTP Auth Pipeline @ 8c │ Cold: 0.97 ms │ Warm: 1.378 ms │ p95: 1.783 ms │ 5,676 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Baseline · 🟢 1.082ms · ↘️ ⚪ stable at 3.00ms (±2.71ms) (3 runs) (2026-08-29 16:18:26) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Firewall · ⚪ 31.860ms · ↗️ 🔴 slower: 9.18ms → 31.86ms (+247%) (7 runs) (2026-08-29 13:06:50) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 67% — check connection pool saturation or lock contention. **Severe degradation** (+247%) — review recent commits immediately.

🏷️ Gateway · 🟢 4.649ms · ↗️ ⚪ stable at 3.03ms (±3.49ms) (2 runs) (2026-08-29 12:55:20) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 55% — check connection pool saturation or lock contention. **Severe degradation** (+53%) — review recent commits immediately.

🏷️ Core · 🟢 4.288ms · ↗️ ⚪ stable at 2.88ms (±2.09ms) (2 runs) (2026-08-29 12:55:20) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 41% — check connection pool saturation or lock contention. **Severe degradation** (+49%) — review recent commits immediately.

🏷️ Cold (DB) · 🟢 1.705ms · ➡️ ⚪ stable at 1.78ms (±2.89ms) (3 runs) (2026-09-02 18:21:28) · source

> ⏳ Pending

🏷️ Warm (Cache) · 🟢 0.538ms · ↘️ ⚪ stable at 0.726ms (±1.03ms) (3 runs) (2026-09-02 18:21:28) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Upload · 🟢 16.614ms · ↗️ ⚪ stable at 13.09ms (±12.59ms) (2 runs) (2026-08-29 13:08:24) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 35% — check connection pool saturation or lock contention. **Severe degradation** (+27%) — review recent commits immediately.

🏷️ Download · 🟢 21.262ms · ↗️ ⚪ stable at 15.15ms (±14.60ms) (2 runs) (2026-08-29 13:08:24) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 40% — check connection pool saturation or lock contention. **Severe degradation** (+40%) — review recent commits immediately.

🏷️ Adapter · 🟢 0.369ms · ↘️ ⚪ stable at 0.573ms (±0.318ms) (5 runs) (2026-08-31 09:11:23) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                            SVELTYCMS — DIRECT ADAPTER THROUGHPUT (SQLITE)                             ║
║                          File: tests/benchmarks/local-api-throughput.test.ts                          ║
║                                       Ran: 2026-08-31 09:11:23                                        ║
║Measures direct adapter write throughput, read throughput, and percentile latencies with zero HTTP overhead.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Writes (1000 atomic increments) │        0.334 ms │ p95:        0.343 ms │ RPS:     17,214 ║
║ Reads (1000 point lookups)     │        0.369 ms │ p95:        0.918 ms │ RPS:    122,078 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ DETACHED · 🟢 0.144ms · ➡️ ⚪ established at 0.144ms (1 run) (2026-08-31 09:11:35) · source

> ⏳ Pending

🏷️ Stability · 🟢 0.670ms · ➡️ ⚪ established at 0.670ms (1 run) (2026-09-02 15:03:26) · source

> ⏳ Pending

🏷️ Storage · 🟢 1.540ms · ↘️ ⚪ stable at 6.07ms (±4.49ms) (3 runs) (2026-08-29 18:01:49) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Large File · 🟢 147.748ms · ↗️ ⚪ stable at 104.89ms (±93.86ms) (2 runs) (2026-08-29 13:08:08) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 43% — check connection pool saturation or lock contention. **Severe degradation** (+41%) — review recent commits immediately.

🏷️ Small File · 🟢 170.481ms · ↘️ ⚪ stable at 207.83ms (±197.59ms) (2 runs) (2026-08-29 13:08:08) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Ingestion · ⚪ 160.087ms · ↗️ 🔴 slower: 45.96ms → 160.09ms (+248%) (2 runs) (2026-08-29 13:08:43) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 85% — check connection pool saturation or lock contention. **Severe degradation** (+248%) — review recent commits immediately.

🏷️ Read (ID) · 🟢 11.277ms · ↗️ ⚪ stable at 7.83ms (±6.45ms) (2 runs) (2026-08-29 13:08:43) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 42% — check connection pool saturation or lock contention. **Severe degradation** (+44%) — review recent commits immediately.

🏷️ Read (Scan) · 🟢 4.044ms · ↗️ ⚪ stable at 2.98ms (±2.87ms) (2 runs) (2026-08-29 13:08:43) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 45% — check connection pool saturation or lock contention. **Severe degradation** (+36%) — review recent commits immediately.

🏷️ Core Engine · 🟢 0.656ms · ↗️ ⚪ stable at 0.431ms (±0.564ms) (2 runs) (2026-08-29 12:57:27) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 63% — check connection pool saturation or lock contention. **Severe degradation** (+52%) — review recent commits immediately.

🏷️ Generation · 🟢 3.337ms · ➡️ ⚪ established at 3.34ms (1 run) (2026-08-29 12:39:17) · source

> ⏳ Pending

🏷️ Cached · ⚪ 3.911ms · ↗️ 🔴 slower: 1.16ms → 3.91ms (+236%) (2 runs) (2026-08-29 12:39:17) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 52% — check connection pool saturation or lock contention. **Severe degradation** (+236%) — review recent commits immediately.

🏷️ Collections · ⚪ 2.207ms · ↘️ 🟢 faster: 5.52ms → 2.21ms (-60%) (4 runs) (2026-08-29 21:12:47) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ DB Join · 🟢 2.302ms · ↘️ ⚪ stable at 5.55ms (±4.34ms) (4 runs) (2026-08-29 21:12:48) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ L1 Cache · ⚪ 1.121ms · ↘️ 🟢 faster: 3.13ms → 1.12ms (-64%) (4 runs) (2026-08-29 21:12:48) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ CRUD (Get) · 🟢 0.928ms · ↘️ ⚪ stable at 0.982ms (±0.558ms) (6 runs) (2026-09-02 19:40:48) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ CRUD (List) · 🟢 0.940ms · ↘️ ⚪ stable at 1.12ms (±0.715ms) (6 runs) (2026-09-02 19:40:48) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ CRUD (Search) · 🟢 0.882ms · ↘️ ⚪ stable at 1.15ms (±1.08ms) (6 runs) (2026-09-02 19:40:49) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Read Path · 🟢 0.740ms · ↘️ ⚪ stable at 2.45ms (±2.14ms) (3 runs) (2026-08-29 16:18:26) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ History · 🟢 0.373ms · ↘️ ⚪ stable at 0.831ms (±1.03ms) (4 runs) (2026-08-29 16:18:26) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Threat Scan · 🟢 0.002ms · ➡️ ⚪ stable at 0.002ms (±0.002ms) (2 runs) (2026-08-29 13:05:52) · source

> ⏳ Pending

🏷️ Audit · 🟢 2.006ms · ➡️ recorded (awaiting trend) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 78% — check connection pool saturation or lock contention. **Severe degradation** (+100%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — PRODUCTION DAY AUDIT                                    ║
║                             File: tests/benchmarks/production-day.test.ts                             ║
║                                       Ran: 2026-08-29 21:32:33                                        ║
║Simulates a realistic multi-user workload with a weighted mix of read, list, update, media, and GraphQL operations with per-tier latency telemetry.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Production Day Composite     │ Cold:     2.95 ms │ Warm:     2.141 ms │ p95:     3.423 ms │     135 RPS ║
║ Day: READ_LIST                 │        2.006 ms │ p95:        3.041 ms │ RPS:        205 ║
║ Day: READ_ENTRY                │        1.875 ms │ p95:        3.218 ms │ RPS:        105 ║
║ Day: UPDATE                    │        2.392 ms │ p95:        3.324 ms │ RPS:        125 ║
║ Day: MEDIA                     │        2.592 ms │ p95:        3.785 ms │ RPS:         58 ║
║ Day: GQL                       │        3.253 ms │ p95:        4.433 ms │ RPS:         26 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Auth Gate · 🟢 ⏳ pending · ➡️ ⚪ stable at 0ms (2 runs) (2026-08-29 13:05:52) · source

> ⏳ Pending

🏷️ State Logic · 🟢 30.898ms · ↘️ ⚪ stable at 34.45ms (±7.41ms) (5 runs) (2026-08-29 13:15:03) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Self-Healing · 🟢 29.325ms · ↘️ ⚪ stable at 33.05ms (±6.10ms) (5 runs) (2026-08-29 13:15:03) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

🏷️ Recovery · ⚪ 3.772ms · ↗️ 🔴 slower: 0.825ms → 3.77ms (+357%) (7 runs) (2026-08-29 13:06:50) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 74% — check connection pool saturation or lock contention. **Severe degradation** (+357%) — review recent commits immediately.

🏷️ AI · 🟢 0.070ms · ➡️ recorded (awaiting trend) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — AI INFRASTRUCTURE AUDIT ║ ║ File: tests/benchmarks/ai-performance.test.ts ║ ║ Ran: 2026-08-29 21:32:16 ║ ║ Measures the latency tax of internal CMS logic for AI enrichment and layout generation. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ AI Text Enrichment │ Cold: 0.07 ms │ Warm: 0.000 ms │ p95: 0.001 ms │ 616,840 RPS ║ ║ AI Layout Spec Generation │ Cold: 0.04 ms │ Warm: 0.000 ms │ p95: 0.001 ms │ 958,160 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ HTTP-Cold · 🟢 0.523ms · ↘️ ⚪ stable at 0.653ms (±0.259ms) (2 runs) (2026-09-02 19:39:10) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

API · 15 tests

🏷️ AI Bus & Inference Overhead · 🟢 0.270ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — AI INFRASTRUCTURE AUDIT                                  ║
║                             File: tests/benchmarks/ai-performance.test.ts                             ║
║                                       Ran: 2026-08-29 12:41:00                                        ║
║        Measures the latency tax of internal CMS logic for AI enrichment and layout generation.        ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ AI Text Enrichment           │ Cold:     0.27 ms │ Warm:     0.001 ms │ p95:     0.004 ms │ 159,422 RPS ║
║ AI Layout Spec Generation    │ Cold:     0.17 ms │ Warm:     0.001 ms │ p95:     0.004 ms │ 222,668 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ temporal integrity · 🟢 2.797ms · ↗️ ⚪ stable at 2.47ms (±0.340ms) (7 runs) (2026-08-30 08:26:09) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 14% — check connection pool saturation or lock contention.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — TEMPORAL INTEGRITY AUDIT                                  ║
║                           File: tests/benchmarks/temporal-integrity.test.ts                           ║
║                                       Ran: 2026-08-30 08:26:09                                        ║
║Validates strict backend UTC normalization (ISO 8601 with trailing 'Z') across global timezone offsets, fractional timezones, and midnight transitions.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Temporal Ingestion & Normalization │ Cold:     4.54 ms │ Warm:     2.797 ms │ p95:     5.935 ms │   1,246 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Core Widgets Overhead · 🟢 0.680ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — WIDGET PIPELINE AUDIT                                   ║
║                           File: tests/benchmarks/widget-performance.test.ts                           ║
║                                       Ran: 2026-08-29 21:32:04                                        ║
║Measures the isolated middleware tax of widget transformations, lifecycle hooks, and validation pipelines across core widget types.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ DB Baseline (No Widgets)     │ Cold:     0.68 ms │ Warm:     0.034 ms │ p95:     0.054 ms │  24,763 RPS ║
║ Widget Pipeline (Local SDK)  │ Cold:     9.75 ms │ Warm:     0.041 ms │ p95:     0.065 ms │  20,469 RPS ║
║ Widget Matrix Dispatch (8 Core) │ Cold:     0.22 ms │ Warm:     0.000 ms │ p95:     0.001 ms │ 1,673,098 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Simulated Admin UX Vitality · 🟢 2.020ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS  —  ADMIN UX VITALITY AUDIT                                 ║
║                           File: tests/benchmarks/admin-ux-vitality.test.ts                            ║
║                                       Ran: 2026-08-29 21:31:38                                        ║
║                    Forms and widget registry performance via real HTTP endpoints.                     ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Schema Resolution (8f)       │ Cold:     2.02 ms │ Warm:     0.847 ms │ p95:     1.469 ms │   4,316 RPS ║
║ Collection List (11 cols)    │ Cold:     4.55 ms │ Warm:     0.844 ms │ p95:     1.252 ms │   4,570 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Entry Edit Hydration · 🟢 0.016ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                SVELTYCMS — ENTRY EDIT HYDRATION AUDIT                                 ║
║                          File: tests/benchmarks/entry-edit-hydration.test.ts                          ║
║                                       Ran: 2026-08-29 21:32:02                                        ║
║     Measures 50-field form mount, dynamic widget prefetch, and reactive field-patch sync latency.     ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ 50-Field Loader Resolve      │ Cold:     0.42 ms │ Warm:     0.021 ms │ p95:     0.036 ms │  37,463 RPS ║
║ Widget Prefetch (5 types)      │        0.016 ms │ p95:        0.034 ms │ RPS:     60,707 ║
║ First Input (field patch)    │ Cold:     0.13 ms │ Warm:     0.000 ms │ p95:     0.000 ms │ 2,149,890 RPS ║
║ First Input (JSON.stringify) │ Cold:     0.14 ms │ Warm:     0.004 ms │ p95:     0.005 ms │ 212,992 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Media Engine & DAM Overhead · 🟢 55.250ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — MEDIA PIPELINE AUDIT                                    ║
║                           File: tests/benchmarks/media-performance.test.ts                            ║
║                                       Ran: 2026-08-29 21:34:37                                        ║
║Measures full upload, Sharp thumbnail processing, SDK vs HTTP latency, and asset streaming throughput. ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ SDK: Media Processing        │ Cold:    55.25 ms │ Warm:    47.039 ms │ p95:    60.031 ms │      41 RPS ║
║ HTTP: Media Upload           │ Cold:    58.02 ms │ Warm:    42.827 ms │ p95:    52.156 ms │      45 RPS ║
║ HTTP: Asset Stream (Thumbnail) │ Cold:     4.31 ms │ Warm:     1.480 ms │ p95:     3.903 ms │   2,092 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Relational & Nested Queries · 🟢 3.080ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — RELATIONAL RESOLVER AUDIT                                 ║
║                         File: tests/benchmarks/relational-performance.test.ts                         ║
║                                       Ran: 2026-08-29 21:31:50                                        ║
║Measures GraphQL resolver performance for shallow listings, deep relational joins, and nested author population across cold/hot execution paths.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Shallow Query (Collections)  │ Cold:     3.08 ms │ Warm:     3.644 ms │ p95:     6.201 ms │   1,535 RPS ║
║ Deep Join (Cold DB)          │ Cold:     3.07 ms │ Warm:     2.747 ms │ p95:     3.700 ms │   1,389 RPS ║
║ Deep Join (Warm Cached)      │ Cold:     2.08 ms │ Warm:     2.093 ms │ p95:     2.955 ms │   1,814 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ OpenAPI Specification Performance · 🟢 0.537ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                               SVELTYCMS — OPENAPI SPEC GENERATION AUDIT                               ║
║                          File: tests/benchmarks/openapi-performance.test.ts                           ║
║                                       Ran: 2026-08-29 21:31:45                                        ║
║Measures in-process dynamic OpenAPI spec generation, HTTP cold generation, and cached documentation endpoint performance.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ In-Process Spec Generation   │ Cold:     2.28 ms │ Warm:     0.582 ms │ p95:     0.694 ms │   1,674 RPS ║
║ HTTP Cold Generation           │        0.537 ms │ p95:        0.781 ms │ RPS:      1,863 ║
║ Warm OpenAPI Hit (Cached)    │ Cold:     1.27 ms │ Warm:     0.976 ms │ p95:     1.572 ms │   3,836 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Auth & RBAC Performance · 🟢 0.711ms · ➡️ recorded (awaiting trend) · source

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                          SVELTYCMS — AUTHENTICATION TELEMETRY                           ║
║                     File: tests/benchmarks/auth-performance.test.ts                     ║
║                                Ran: 2026-08-28 09:42:21                                 ║
║    Evaluates authenticated session resolution, RBAC evaluation, and rejection paths.    ║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ Unauthenticated (401 Fast Path) │        0.711 ms │ p95:        2.347 ms │ RPS:      1,194 ║
║ Auth Validation @ 1c           │        0.517 ms │ p95:        0.751 ms │ RPS:      1,688 ║
║ HTTP Auth Pipeline @ 8c        │        2.460 ms │ p95:        3.951 ms │ RPS:      3,089 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Security · 🟢 0.439ms · ➡️ ⚪ stable at 0.426ms (±0.014ms) (7 runs) (2026-09-02 19:57:33) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — SECURITY INFRASTRUCTURE AUDIT ║ ║ File: tests/benchmarks/security-audit.test.ts ║ ║ Ran: 2026-08-29 21:34:05 ║ ║Measures overhead of WAF request analysis (clean & malicious), audit log persistence, Argon2id password hashing, and RBAC permission checks.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ WAF Deep Analysis (Clean) │ Cold: 0.14 ms │ Warm: 0.001 ms │ p95: 0.005 ms │ 509,765 RPS ║ ║ WAF Inspect (Clean Query) │ Cold: 0.34 ms │ Warm: 0.000 ms │ p95: 0.000 ms │ 1,567,982 RPS ║ ║ WAF Inspect (Malicious Probe) │ Cold: 0.18 ms │ Warm: 0.001 ms │ p95: 0.002 ms │ 651,344 RPS ║ ║ Audit Log Dispatch (Disabled Fast-Path) │ Cold: 0.25 ms │ Warm: 0.000 ms │ p95: 0.001 ms │ 1,311,762 RPS ║ ║ Argon2id Password Hashing │ Cold: 4.85 ms │ Warm: 0.520 ms │ p95: 0.729 ms │ 1,897 RPS ║ ║ Dispatcher Permission Check │ Cold: 0.48 ms │ Warm: 0.000 ms │ p95: 0.001 ms │ 1,062,805 RPS ║ ║ Full Defense-in-Depth (Gate + Handler) │ Cold: 0.10 ms │ Warm: 0.001 ms │ p95: 0.001 ms │ 1,154,126 RPS ║ ║ Admin Fast-Path Verification │ Cold: 0.10 ms │ Warm: 0.000 ms │ p95: 0.000 ms │ 3,130,993 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ REST API Performance · 🟢 2.380ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — ENTERPRISE REST API AUDIT                                 ║
║                          File: tests/benchmarks/rest-api-performance.test.ts                          ║
║                                       Ran: 2026-09-02 19:40:49                                        ║
║Measures latency, throughput, and correctness of core REST endpoints: health check, schema, single read, list, and search.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ System Health Check          │ Cold:     2.38 ms │ Warm:     0.786 ms │ p95:     2.092 ms │   4,273 RPS ║
║ Collection Schema Metadata   │ Cold:     3.35 ms │ Warm:     0.900 ms │ p95:     2.104 ms │   3,856 RPS ║
║ Single Document Read         │ Cold:     1.47 ms │ Warm:     0.928 ms │ p95:     2.089 ms │   3,838 RPS ║
║ Collection Find (List Limit 20) │ Cold:     6.66 ms │ Warm:     0.940 ms │ p95:     2.026 ms │   3,813 RPS ║
║ Collection Search Query      │ Cold:     4.46 ms │ Warm:     0.882 ms │ p95:     1.933 ms │   4,037 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ GraphQL API Performance · 🟢 1.840ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — GRAPHQL PERFORMANCE AUDIT                                 ║
║                        File: tests/benchmarks/graphql-api-performance.test.ts                         ║
║                                       Ran: 2026-09-02 19:57:42                                        ║
║Measures GraphQL resolver performance across cold (cache-bypassed) and hot (response-cache hit) execution paths.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ GQL: System Health [cold]    │ Cold:     1.84 ms │ Warm:     0.496 ms │ p95:     0.682 ms │   1,860 RPS ║
║ GQL: System Health [hot]     │ Cold:     0.60 ms │ Warm:     0.349 ms │ p95:     0.442 ms │   2,723 RPS ║
║ GQL: Collection List [cold]  │ Cold:     0.97 ms │ Warm:     1.689 ms │ p95:     2.247 ms │   3,312 RPS ║
║ GQL: Collection List [hot]   │ Cold:     0.39 ms │ Warm:     1.313 ms │ p95:     1.674 ms │   4,262 RPS ║
║ GQL: Parameterized Query [cold] │ Cold:     1.17 ms │ Warm:     2.471 ms │ p95:     3.878 ms │   2,971 RPS ║
║ GQL: Parameterized Query [hot] │ Cold:     0.45 ms │ Warm:     1.589 ms │ p95:     2.233 ms │   4,563 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Enterprise SEO Suite Audit · 🟢 1.540ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — ENTERPRISE SEO AUDIT                                    ║
║                            File: tests/benchmarks/seo-performance.test.ts                             ║
║                                       Ran: 2026-08-29 21:31:55                                        ║
║Measures redirect lookup latency, dynamic sitemap.xml generation, robots.txt serving, and 404 logging performance.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Redirect Lookup (301)        │ Cold:     1.54 ms │ Warm:     1.582 ms │ p95:     3.269 ms │   5,001 RPS ║
║ Dynamic Sitemap XML          │ Cold:    40.13 ms │ Warm:     1.036 ms │ p95:     1.886 ms │   7,638 RPS ║
║ Robots.txt Generation        │ Cold:     2.57 ms │ Warm:     2.032 ms │ p95:     3.850 ms │   3,890 RPS ║
║ Missing Path (404 Log)       │ Cold:    47.84 ms │ Warm:    20.226 ms │ p95:    24.985 ms │     395 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ websocket broadcast · 🟢 6.930ms · ➡️ recorded (awaiting trend) · source

> [!NOTE] > **Specific to this test**: Avg degraded but p95 stable — possible cold-start effect, GC pause, or warmup variance. Throughput dropped 66% — check connection pool saturation or lock contention. **Severe degradation** (+210%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                               SVELTYCMS — YJS COLLABORATION SYNC AUDIT                                ║
║                          File: tests/benchmarks/websocket-broadcast.test.ts                           ║
║                                       Ran: 2026-08-29 21:35:30                                        ║
║Measures WebSocket handshake latency, bidirectional Yjs CRDT update propagation, and synchronization throughput.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ WS Handshake + SyncStep        │        6.930 ms │ p95:        0.000 ms │ RPS:          0 ║
║ Yjs CRDT Propagation         │ Cold:     1.80 ms │ Warm:     0.124 ms │ p95:     0.237 ms │   6,799 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ WebSocket & Realtime Latency · ⏳ pending · ➡️ baseline · source

Scale · 20 tests

🏷️ Negative Cache Performance · ⏳ pending · ➡️ baseline · source

🏷️ Revision & History Growth · 🟢 0.888ms · ➡️ recorded (awaiting trend) · source

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                            SVELTYCMS — REVISION STRESS AUDIT                            ║
║                     File: tests/benchmarks/revision-stress.test.ts                      ║
║                                Ran: 2026-08-11 22:07:53                                 ║
║Measures read and history list latency degradation under heavy revision history growth (100 revisions per entry).║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ Latest Read (High Revision Count) │        0.888 ms │ p95:        1.917 ms │ RPS:      1,127 ║
║ History List Retrieval         │        0.543 ms │ p95:        0.866 ms │ RPS:      1,841 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Memory Stability & GC Behavior · ⚪ ⏳ pending · ➡️ pending · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — MEMORY STABILITY AUDIT                                   ║
║                            File: tests/benchmarks/memory-stability.test.ts                            ║
║                                       Ran: 2026-09-02 11:56:58                                        ║
║Tracks RSS, heap, and external memory growth under sustained mixed load with automated regression leak detection.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Memory Profile                 │        0.000 ms │ p95:        0.000 ms │ RPS:        446 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Multi-Tenant Performance & Isolation · ⏳ pending · ➡️ baseline · source

🏷️ mixed workload · 🟢 1.782ms · ➡️ recorded (awaiting trend) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — MIXED WORKLOAD AUDIT                                    ║
║                             File: tests/benchmarks/mixed-workload.test.ts                             ║
║                                       Ran: 2026-08-29 21:31:58                                        ║
║Simulates real-world traffic with a weighted mix of reads, searches, GraphQL queries, and metadata requests with per-operation telemetry.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Mixed Workload               │ Cold:     4.12 ms │ Warm:     1.848 ms │ p95:     5.185 ms │   3,442 RPS ║
║ Mix: REST Read                 │        1.782 ms │ p95:        2.683 ms │ RPS:        414 ║
║ Mix: REST Search               │        1.806 ms │ p95:        2.745 ms │ RPS:        136 ║
║ Mix: GraphQL                   │        4.593 ms │ p95:        6.642 ms │ RPS:        103 ║
║ Mix: Metadata                  │        1.732 ms │ p95:        2.569 ms │ RPS:         31 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ GraphQL Load Stress · 🟢 3.540ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                SVELTYCMS — GRAPHQL CAPACITY DISCOVERY                                 ║
║                             File: tests/benchmarks/graphql-stress.test.ts                             ║
║                                       Ran: 2026-09-02 18:21:18                                        ║
║                Discovers maximum sustainable GraphQL throughput by ramping concurrency                ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ GQL: 5c Warmup               │ Cold:     3.54 ms │ Warm:     2.118 ms │ p95:     3.526 ms │   2,159 RPS ║
║ GQL: 10c Light               │ Cold:     1.15 ms │ Warm:     3.374 ms │ p95:     6.982 ms │   2,674 RPS ║
║ GQL: 20c Moderate            │ Cold:     0.96 ms │ Warm:     4.893 ms │ p95:     8.482 ms │   3,865 RPS ║
║ GQL: 40c Heavy               │ Cold:     0.95 ms │ Warm:     8.962 ms │ p95:    13.505 ms │   4,102 RPS ║
║ GQL: 60c Stress              │ Cold:     0.84 ms │ Warm:    13.255 ms │ p95:    17.788 ms │   4,295 RPS ║
║ GQL: 80c Extreme             │ Cold:     0.83 ms │ Warm:    17.461 ms │ p95:    22.090 ms │   4,548 RPS ║
║ GQL: 100c Max                │ Cold:     0.86 ms │ Warm:    20.136 ms │ p95:    25.477 ms │   4,719 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ migration scale · 🟢 75.070ms · ➡️ recorded (awaiting trend) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — MIGRATION & SCALE AUDIT ║ ║ File: tests/benchmarks/migration-scale.test.ts ║ ║ Ran: 2026-08-29 21:34:56 ║ ║Measures bulk ingestion throughput for 10,000 entries, random point-lookups, and indexed range scans across large datasets.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Bulk Migration (10k docs) │ Cold: 75.07 ms │ Warm: 44.224 ms │ p95: 64.561 ms │ 10,672 RPS ║ ║ Random Point Lookup │ Cold: 4.85 ms │ Warm: 4.131 ms │ p95: 6.096 ms │ 1,384 RPS ║ ║ Range Scan & Pagination │ Cold: 14.37 ms │ Warm: 1.334 ms │ p95: 1.644 ms │ 4,338 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ index pressure · 🟢 132.890ms · ➡️ recorded (awaiting trend) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 49% — check connection pool saturation or lock contention. **Severe degradation** (+37%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS  —  INDEX PRESSURE AUDIT                                   ║
║                             File: tests/benchmarks/index-pressure.test.ts                             ║
║                                       Ran: 2026-08-29 21:32:56                                        ║
║           Measures read performance with sorting and filtering on a large entry collection.           ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Sorted List (25k rows)       │ Cold:   132.89 ms │ Warm:     0.542 ms │ p95:     0.807 ms │   1,831 RPS ║
║ Filtered Query (25k rows)    │ Cold:     8.16 ms │ Warm:     0.504 ms │ p95:     0.635 ms │   1,975 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Content Scale Stress · 🟢 1.557ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                SVELTYCMS — CONTENT SCALE STRESS AUDIT                                 ║
║                          File: tests/benchmarks/content-scale-stress.test.ts                          ║
║                                       Ran: 2026-08-29 21:34:21                                        ║
║        Measures file-scanning and content discovery performance at scale (1,000+ collections).        ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Cold Stress Scan (1000 files)  │        1.557 ms │ p95:        2.393 ms │ RPS:        642 ║
║ Warm Stress Scan (1000 files) │ Cold:     0.52 ms │ Warm:     0.179 ms │ p95:     0.227 ms │   5,116 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Media Upload Stress & Throughput · 🟢 43.560ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — MEDIA UPLOAD STRESS AUDIT                                 ║
║                          File: tests/benchmarks/media-upload-stress.test.ts                           ║
║                                       Ran: 2026-08-29 21:34:44                                        ║
║Measures throughput for large file uploads, concurrent transfers, and streaming efficiency with valid media fixtures.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Single Upload (0.01MB)       │ Cold:    43.56 ms │ Warm:    38.299 ms │ p95:    41.435 ms │      26 RPS ║
║ Small Upload (0MB @ 4c)      │ Cold:    56.13 ms │ Warm:    99.006 ms │ p95:   108.014 ms │      40 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ client journey · 🟢 2.187ms · ↘️ ⚪ stable at 9.78ms (±6.25ms) (4 runs) (2026-09-02 17:32:47) · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                     SVELTYCMS  —  WORLD LIFE DATA                                     ║
║                             File: tests/benchmarks/client-journey.test.ts                             ║
║                                       Ran: 2026-09-02 17:32:47                                        ║
║ Measures cumulative latency of a realistic editorial user workflow: Auth → List → View → Edit → Save. ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Full Journey @ 1c            │ Cold:    11.80 ms │ Warm:     2.187 ms │ p95:     2.505 ms │     455 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ concurrency max · 🟢 9.574ms · ➡️ recorded (awaiting trend) · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits. Throughput dropped 29% — check connection pool saturation or lock contention. **Severe degradation** (+78857%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                SVELTYCMS — THROUGHPUT SCALING (SQLITE)                                ║
║                         File: tests/benchmarks/concurrency-throughput.test.ts                         ║
║                                       Ran: 2026-08-29 21:35:03                                        ║
║          Phased wave writes across 10 / 100 / 1000 documents with inline stream consumption.          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ 10 docs × 10 (100 writes)      │        9.574 ms │ p95:       29.865 ms │ RPS:        461 ║
║ 100 docs × 1 (100 writes)      │        6.777 ms │ p95:       11.791 ms │ RPS:        497 ║
║ 1000 docs × 1 (1000 writes)    │        7.664 ms │ p95:       14.341 ms │ RPS:        416 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Multi-Doc Concurrency Throughput · ⏳ pending · ➡️ baseline · source

🏷️ Max Throughput — No Throttle · ⏳ pending · ➡️ baseline · source

🏷️ Local SDK Throughput · ⏳ pending · ➡️ baseline · source

🏷️ Failure Propagation & Fast-Fail Audit · ⏳ pending · ➡️ baseline · source

🏷️ Chaos & Infrastructure Resilience · 🟢 3.950ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — CIRCUIT BREAKER AUDIT                                   ║
║                        File: tests/benchmarks/circuit-breaker-failover.test.ts                        ║
║                                       Ran: 2026-08-29 12:55:29                                        ║
║Simulates external service failures and measures system graceful degradation via circuit breaker patterns.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Circuit Breaker Fallback     │ Cold:     3.95 ms │ Warm:     2.072 ms │ p95:     5.310 ms │     930 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Production Day Simulation · ⏳ pending · ➡️ baseline · source

🏷️ Longevity Soak (Memory Stability) · 🟢 0.670ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — LONGEVITY SOAK AUDIT                                    ║
║                             File: tests/benchmarks/longevity-soak.test.ts                             ║
║                                       Ran: 2026-09-02 15:03:26                                        ║
║     Sustained mixed read/write workload over configurable hours with periodic memory/CPU sampling     ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ 0.08h Longevity Soak           │        0.670 ms │ p95:        1.090 ms │ RPS:         97 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Large Payload Streaming · 🟢 5.980ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                               SVELTYCMS — LARGE PAYLOAD STREAMING AUDIT                               ║
║                        File: tests/benchmarks/large-payload-streaming.test.ts                         ║
║                                       Ran: 2026-08-29 21:34:48                                        ║
║Measures upload/download throughput, zero-buffer streaming, and memory efficiency under large payloads.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Upload 0.5MB                 │ Cold:     5.98 ms │ Warm:     3.834 ms │ p95:     4.589 ms │     258 RPS ║
║ Download 0.5MB               │ Cold:     4.26 ms │ Warm:     3.827 ms │ p95:     7.724 ms │     760 RPS ║
║ Upload 1MB                   │ Cold:     6.60 ms │ Warm:     6.145 ms │ p95:    10.363 ms │     149 RPS ║
║ Download 1MB                 │ Cold:     3.85 ms │ Warm:     6.353 ms │ p95:     9.692 ms │     577 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

Resilience · 5 tests

🏷️ Circuit Breaker Failover · ⏳ pending · ➡️ baseline · source

🏷️ Throttling & Backoff Stress · 🟢 2.907ms · ➡️ recorded (awaiting trend) · source

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                              SVELTYCMS — THROTTLING AUDIT                               ║
║                File: tests/benchmarks/throttling-backoff-stress.test.ts                 ║
║                                Ran: 2026-08-11 20:01:20                                 ║
║Simulates high-velocity traffic from a single client IP to verify rate-limiting enforcement and backoff consistency.║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ Throttling Enforcement         │        2.907 ms │ p95:        6.843 ms │ RPS:        344 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Data Residency & Sovereignty · ⏳ pending · ➡️ baseline · source

🏷️ Database Failover & Reconnection · 🟢 13.935ms · ➡️ recorded (awaiting trend) · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                             SVELTYCMS — REINITIALIZE RESILIENCE (SQLite)                              ║
║                           File: tests/benchmarks/database-failover.test.ts                            ║
║                                       Ran: 2026-09-02 18:14:21                                        ║
║        Simulates database connection loss mid-request and measures circuit breaker activation,        ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Reinitialize Recovery          │       13.935 ms │ p95:       13.935 ms │ RPS:          0 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝