PostgreSQL Performance Audit

Database performance benchmarks with trend analysis and competitive context.

7/4/2026

45 min read

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 --sql) always records.

📊 Latest Performance Audit

📝 Fix Overlays

Note

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

(21/10/2026, 18:34:46)

✅ PASS · 38/45 tests · 7 skipped · POSTGRESQL · Bun 1.4.2

Dimension health

Dimension	Tests	Status	Worst Δ
Core	13	🟢	+1048%
API	9	🟢	+68%
Scale	18	🟢	-100%
Resilience	5	🟢	—

Issues (action required)

✅ All clear — no regressions or budget violations detected.

Executive latency matrix

Scenario	Latency	Trend	Budget	Result
Cold Start	N/A	⚪ (—)	< 5000ms	⚪ N/A
REST (Collections)	N/A	⚪ (—)	< 5ms	⚪ N/A
Middleware Hooks	N/A	⚪	< 2ms	⚪ N/A
GraphQL (Avg)	N/A	⚪ (—)	< 5ms	⚪ N/A
Million-Row Index	N/A	⚪	< 250ms	⚪ N/A
DB Raw (p95)	N/A	⚪	< 50ms	⚪ N/A

Historical pulse

Scope: Sparklines only — full run tables: tests/benchmarks/results/history.sqlite

Metric	Trend	Sparkline	Latest

📈 Latency trend chart (last 10 runs)

xychart-beta title "POSTGRESQL 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]

📊 Regression severity matrix (quadrant)

quadrantChart title "Regression severity (impact vs delta)" x-axis Low latency impact --> High latency impact y-axis Low delta --> High delta quadrant-1 Monitor quadrant-2 Investigate soon quadrant-3 Acceptable variance quadrant-4 Critical — fix first API LAYER LATENCY: [0.05, 0.95] COMPETITIVE 9-WORKLOAD REPLI: [0.05, 0.19] MIDDLEWARE FLAMEGRAPH PROFIL: [0.05, 0.11] Incremental Content Reload: [0.05, 0.13] Middleware & Hooks Performan: [0.05, 0.05] State Machine Transitions: [0.95, 0.06] Database Adapter Raw CRUD: [0.05, 0.13] ACID Transaction Overhead: [0.05, 0.15]

📋 Partial report — run full matrix for complete cross-DB analysis.

🔴 Top Regressions

🔴 database-performance [QUERY BUILDER LIST (50)] (postgresql): +132% | 4.35ms vs 1.88ms baseline 🔴 media-performance [SDK: Media Processing] (postgresql): +90% | 95.14ms vs 50.01ms baseline 🔴 media-performance [HTTP: Media Upload] (postgresql): +71% | 75.98ms vs 44.43ms baseline 🔴 state-machine-transition [Self-Healing Full Convergence] (postgresql): +65% | 108.11ms vs 65.71ms baseline 🔴 state-machine-transition [State Transition (Transient)] (postgresql): +64% | 111.02ms vs 67.54ms baseline

🟢 Top Improvements

local-cms-crud [LocalCMS create] (postgresql): -78% | 0.50ms vs 2.30ms baseline local-cms-crud [LocalCMS update] (postgresql): -76% | 0.54ms vs 2.23ms baseline local-cms-crud [LocalCMS mixed C/U/R] (postgresql): -73% | 1.40ms vs 5.26ms baseline sharp-vs-bun-image [Bun.Image Metadata (header-only)] (postgresql): -67% | 0.01ms vs 0.02ms baseline scale-spectrum [listFilterSort @ 5000] (postgresql): -66% | 0.63ms vs 1.84ms baseline

Current Run Summary (2026-10-17)

Scope: Only tests that ran in THIS invocation.

⚠️ Executive PASS/FAIL reflects the last full matrix run.

Run ID: 01a14a7a-e189-706c-b2eb-aaca8a49dd96 · Tests invoked: 1 · Metrics: 2 · DB: postgresql

Test	Metric	Avg (ms)	p95 (ms)	RPS	Trend	Detail
Cache Performance	Cache Miss (Bypass)	0.755	0.966	1272	🟢	⚪ established at 0.755ms (1 run)
Cache Performance	Cache Hit (L1 Warm)	0.189	0.267	5138	🟢	⚪ established at 0.189ms (1 run)

Historical Trends (2026-10-21)

Mode: production-parity matrix runs only (run_mode='matrix' + server_mode='production' — NODE_ENV=production, no TEST_MODE). Standalone/mode-variant samples are recorded but never trended here.

Scope: Sparklines only — full run tables live in history.sqlite (link below). Runs = sparkline bar count.

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

Series: 53 · DB: postgresql

Metric	Trend	Sparkline (last 7)	Latest
ADMIN UX VITALITY (warm)	🟢	`▇▁█▂`	0.520ms
AI PERFORMANCE (warm)	🟢	`▁▁▁▁`	0.000ms
AUTH PERFORMANCE (warm)	🟢	`▁▄█▄▅▅`	1.122ms
AUTH SESSION AMR (warm)	🟢	`█▆▅▁▁▁▃`	0.880ms
BUILD ANALYSIS (warm)	🟢	`▁▁`	0.000ms
CACHE HIT RATIO (warm)	🟢	`▆▁█▄▅▁█`	1.321ms
CACHE PERFORMANCE (warm)	🟢	`▁█▁▇`	0.750ms
CACHE SERVICE (warm)	🟢	`▁▆█▁▅▆`	0.655ms
CLIENT JOURNEY (warm)	🟢	`█▁`	5.719ms
COMPETITIVE WORKLOAD REPLICA (warm)	🟢	`▁▂▁▇▄█▄`	0.861ms
CONCURRENCY MAX (warm)	🟢	`█▁`	22.034ms
CONFIG PROMOTION (warm)	🟢	`▁▁▁▁█▁▁`	9.020ms
CONTENT GUI SAVE (warm)	🟢	`█▁`	1.413ms
CONTENT INCREMENTAL RELOAD (warm)	🟢	`▂▁█▃▂▁▅`	0.514ms
CONTENT SCALE STRESS (warm)	🟢	`█▁▇▁`	0.134ms
CONTENT SCAN (warm)	🟢	`█▂▆▁`	0.643ms
DATABASE PERFORMANCE (warm)	🟢	`▂█▁▁▆█▆`	3.555ms
ENTRY EDIT HYDRATION (warm)	🟢	`▁▁▆█▁▁▅`	0.015ms
GRAPHQL API PERFORMANCE (warm)	🟢	`▂▆▄█▆▁▁`	0.724ms
GRAPHQL CACHE HIT (warm)	🟢	`▁▃▂█▁▃▁`	1.002ms
GRAPHQL LOCAL SDK (warm)	🟢	`█▁▆▁`	0.000ms
GRAPHQL STRESS (warm)	🟢	`█▁▂▃▁▄▆`	10.161ms
HOOKS PERFORMANCE (warm)	🟢	`▆▅▁█▁▄▄`	0.792ms
LOCAL API THROUGHPUT (warm)	🟢	`▂█▁▄`	1.620ms
LOCAL CMS CRUD (warm)	🟢	`▃▃▃▃▁█▄`	0.535ms
LOCAL SDK VS DIRECT (warm)	🟢	`▁▁█▇█▇█`	1.486ms
MEDIA UPLOAD STRESS (warm)	🟢	`▆█▁▃`	5.908ms
MEMORY COUNTERS (warm)	🟢	`▁▁`	0.000ms
MIDDLEWARE FLAMEGRAPH (warm)	🟢	`▄▃▃█▁▁█`	1.432ms
MIXED WORKLOAD (warm)	🟢	`█▁`	0.798ms
MULTI TENANT PERFORMANCE (warm)	🟢	`▁█`	0.826ms
OPENAPI PERFORMANCE (warm)	🟢	`▅▁▆▆▁█`	2.056ms
PRODUCTION DAY (warm)	🟢	`█▁`	1.799ms
REALTIME PERFORMANCE (warm)	🟢	`▁▁▁▁▁▁`	0.000ms
REVISION STRESS (warm)	🟢	`▂█▁▁█▁`	0.446ms
RIGHT TO BE FORGOTTEN AUDIT (warm)	🟢	`█▁`	12.657ms
SCALE SPECTRUM (warm)	🟢	`▆▃▂▅▄▁█`	0.849ms
SECURITY AUDIT (warm)	🟢	`█▁▁▁▁▁▁`	0.001ms
STATE MACHINE TRANSITION (warm)	🟢	`▁▁██`	111.017ms
TELEMETRY PERFORMANCE (warm)	🟢	`█▁█▁`	0.000ms
TEMPORAL INTEGRITY (warm)	🟢	`█▁`	2.923ms
TRANSACTION ACID (warm)	🟢	`▁█▁▇`	1.935ms
TRUTH LATENCY (warm)	🟢	`▂▁▁█▃▁▁`	0.000ms
WEBSOCKET BROADCAST (warm)	🟢	`▁█`	0.142ms
WIDGET PERFORMANCE (warm)	🟢	`▇▁▄█▁▄`	0.945ms
API LATENCY (warm)	⚪	`▁█▅▂▁▁█`	4.120ms
INDEX PRESSURE (warm)	⚪	`▂▁▁█`	0.837ms
LARGE PAYLOAD STREAMING (warm)	⚪	`▆▆█▁▄▄█`	11.287ms
LOCAL API PERFORMANCE (warm)	⚪	`█▇▇▄▁▂`	0.407ms
MEDIA PERFORMANCE (warm)	⚪	`▁▇▁▄▂▁█`	95.145ms
NEGATIVE CACHE (warm)	⚪	`██▁▇▇▁`	0.001ms
REST API PERFORMANCE (warm)	⚪	`▂█▄▁▃▁█`	0.859ms
SHARP VS BUN IMAGE (warm)	⚪	`▅▄▁▁▁██`	55.676ms

📊 Infrastructure drill-down (expand for adapter, hooks, memory trends)

📊 Infrastructure drill-down

🏷️ Mixed Workload Performance {#mixedAvg}

Mixed p95: — (not measured in this run) | Trend: ⚪ (—)

Production request mix: 60% Reads, 20% Writes, 15% GraphQL, 5% Media.

🏷️ Database Adapter Performance {#dbRaw}

Raw Adapter p95: — (not measured in this run) | Target: < 50ms | Trend: ⚪ (—)

Direct database access latency (bypass CMS logic).

🏷️ Middleware & Hooks Audit {#hooks}

Middleware p95: — (not measured in this run) | Target: < 2ms | Trend: ⚪ (—)

Total overhead of security, logging, and auth hooks.

🏷️ Memory Stability Audit {#memGrowth}

Memory RSS Δ: — (not measured in this run) | Target: < 60MB | Trend: ⚪ (—)

Peak memory growth during stress workload.

Enterprise scale audit

🏷️ Multi-Tenancy Performance {#tenancyAvg}

Tenancy p95: — (not measured in this run) | Trend: ⚪ (—)

Measures latency across tenant isolation boundaries.

🏷️ Relational Resolver Latency {#relationalAvg}

Relational p95: — (not measured in this run) | Trend: ⚪ (—)

Tests performance of complex JOINs and nested relationship population.

🏷️ Telemetry & Update Performance {#telemetryAvg}

Telemetry p95: — (not measured in this run) | Trend: ⚪ (—)

Measures overhead of telemetry collection and cryptographic signing.

🔬 Full benchmark ledger (41 modules)

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

Core · 27 tests

🏷️ API LAYER LATENCY · ⚪ 4.120ms · ↗️ — · 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 86% — check connection pool saturation or lock contention. **Severe degradation** (+1048%) — review recent commits immediately. > **Check**: `src/routes/api/[...path]/+server.ts` · `src/hooks.server.ts`

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                     SVELTYCMS — API LAYER LATENCY                                     ║
║                              File: tests/benchmarks/api-latency.test.ts                               ║
║                                       Ran: 2026-10-06 10:55:22                                        ║
║              Cold full-pipeline findById + warm TURBO-HIT path after responseCache fill.              ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ HTTP: findById @ 8c (Cold)   │ Cold:     2.36 ms │ Warm:     2.080 ms │ p95:     4.527 ms │   3,371 RPS ║
║ HTTP: findById TURBO-HIT @ 8c (Warm) │ Cold:     0.29 ms │ Warm:     0.753 ms │ p95:     0.881 ms │  10,973 RPS ║
║ HTTP: zstd large GET (>64KiB, drained) │ Cold:     2.84 ms │ Warm:     3.818 ms │ p95:     4.551 ms │     510 RPS ║
║ HTTP: findById TURBO-HIT idle (Warm) │        0.198 ms │ p95:        0.277 ms │ RPS:      4,946 ║
║ HTTP: findById TURBO-HIT during zstd (Warm) │        0.291 ms │ p95:        0.610 ms │ RPS:      2,463 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ PHASED COLD START · ⚪ ⏳ pending · ➡️ — · source

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

🏷️ SRE TRUTH AUDIT · ⚪ ⏳ pending · ↘️ — · source

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                      SVELTYCMS — SRE TRUTH AUDIT                                      ║
║                             File: tests/benchmarks/truth-latency.test.ts                              ║
║                                       Ran: 2026-10-17 12:06:40                                        ║
║            Validates performance claims by comparing SDK, Middleware, and Real HTTP Stack             ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Logic Baseline               │ Cold:     0.01 ms │ Warm:     0.000 ms │ p95:     0.001 ms │ 293,370 RPS ║
║ Local SDK (Full)             │ Cold:     4.98 ms │ Warm:     0.008 ms │ p95:     0.016 ms │  97,685 RPS ║
║ HTTP End-to-End              │ Cold:     8.94 ms │ Warm:     0.439 ms │ p95:     0.593 ms │   2,262 RPS ║
║ HTTP Cold (Cache-Busted)     │ Cold:    13.24 ms │ Warm:     2.014 ms │ p95:     2.736 ms │     496 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Incremental Content Reload · ⚪ 0.514ms · ↗️ — · 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 69% — check connection pool saturation or lock contention. **Severe degradation** (+135%) — review recent commits immediately. > **Check**: `src/content/engine.server.ts` · `src/routes/api/[...path]/handlers/content.ts`

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                             SVELTYCMS — INCREMENTAL CONTENT RELOAD AUDIT                              ║
║                       File: tests/benchmarks/content-incremental-reload.test.ts                       ║
║                                       Ran: 2026-10-06 09:39:27                                        ║
║      Measures surgical single-file fullReload vs full reconciliation path and batch processing.       ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Incremental fullReload (1 file) │ Cold:     4.56 ms │ Warm:     0.060 ms │ p95:     0.129 ms │  14,319 RPS ║
║ Full Reconciliation Reload   │ Cold:     3.12 ms │ Warm:     0.178 ms │ p95:     0.212 ms │   5,543 RPS ║
║ Sequential 10-File Reload    │ Cold:     4.15 ms │ Warm:     0.514 ms │ p95:     0.653 ms │   1,905 RPS ║
║ Batched 10-File Reload       │ Cold:     0.98 ms │ Warm:     0.234 ms │ p95:     0.339 ms │   3,953 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Middleware & Hooks Performance · ⚪ 0.792ms · ↘️ — · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective. Throughput dropped 13% — check connection pool saturation or lock contention.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — MIDDLEWARE & HOOKS AUDIT                                  ║
║                           File: tests/benchmarks/hooks-performance.test.ts                            ║
║                                       Ran: 2026-10-06 10:56:56                                        ║
║Measures the cost of the full middleware chain including Turbo, Security, Auth, and Audit via HTTP E2E.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Static Asset (No Middleware) │ Cold:     2.25 ms │ Warm:     1.057 ms │ p95:     1.939 ms │   3,630 RPS ║
║ Turbo Pipeline (Light)       │ Cold:     0.63 ms │ Warm:     0.785 ms │ p95:     1.182 ms │   4,939 RPS ║
║ Full Security + Auth Pipeline │ Cold:     3.42 ms │ Warm:     0.488 ms │ p95:     1.007 ms │   7,329 RPS ║
║ REST with API Caching        │ Cold:     4.89 ms │ Warm:     0.439 ms │ p95:     0.673 ms │   8,672 RPS ║
║ Mutation (audit logging disabled) │ Cold:     8.52 ms │ Warm:     1.456 ms │ p95:     2.590 ms │     623 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ State Machine Transitions · ⚪ 111.017ms · ↗️ — · 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 31% — check connection pool saturation or lock contention. **Severe degradation** (+64%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — STATE MACHINE INTEGRITY                                  ║
║                        File: tests/benchmarks/state-machine-transition.test.ts                        ║
║                                       Ran: 2026-10-06 09:39:41                                        ║
║Measures state machine self-healing transition latencies, convergence settling time, and health probe consistency under stress.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ State Transition (Transient) │ Cold:   157.07 ms │ Warm:   111.017 ms │ p95:   126.051 ms │       9 RPS ║
║ Self-Healing Full Convergence │ Cold:   116.23 ms │ Warm:   108.114 ms │ p95:   118.538 ms │       9 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Database Adapter Raw CRUD · ⚪ 3.555ms · ↗️ — · 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 73% — check connection pool saturation or lock contention. **Severe degradation** (+132%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                         SVELTYCMS — DATABASE ADAPTER PERFORMANCE (POSTGRESQL)                         ║
║                          File: tests/benchmarks/database-performance.test.ts                          ║
║                                       Ran: 2026-10-06 16:16:27                                        ║
║          Measures raw CRUD performance, indexing efficiency, and connection pool resilience.          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ INSERT                       │ Cold:     2.37 ms │ Warm:     0.504 ms │ p95:     0.893 ms │   1,832 RPS ║
║ FIND ONE                     │ Cold:     2.83 ms │ Warm:     0.382 ms │ p95:     0.731 ms │   2,369 RPS ║
║ FIND MANY (limit 50)         │ Cold:     4.20 ms │ Warm:     0.793 ms │ p95:     1.327 ms │   1,135 RPS ║
║ FILTER (blob field, 1 match) │ Cold:     6.22 ms │ Warm:     1.911 ms │ p95:     2.765 ms │     506 RPS ║
║ QUERY BUILDER LIST (50)      │ Cold:     5.76 ms │ Warm:     0.755 ms │ p95:     1.161 ms │   1,204 RPS ║
║ FIND PAGE (50 hasMore)       │ Cold:     3.90 ms │ Warm:     0.774 ms │ p95:     1.084 ms │   1,228 RPS ║
║ FIND PAGE keyset             │ Cold:    11.98 ms │ Warm:     1.110 ms │ p95:     1.523 ms │     851 RPS ║
║ FIND MANY offset 50          │ Cold:     3.70 ms │ Warm:     0.554 ms │ p95:     0.797 ms │   1,728 RPS ║
║ LIST+COUNT (legacy)          │ Cold:    13.04 ms │ Warm:     2.370 ms │ p95:     2.859 ms │     411 RPS ║
║ UPDATE                       │ Cold:     4.54 ms │ Warm:     0.446 ms │ p95:     0.650 ms │   2,100 RPS ║
║ UPDATE (no-returning)        │ Cold:     2.76 ms │ Warm:     0.393 ms │ p95:     0.574 ms │   2,403 RPS ║
║ NATIVE UPSERT                │ Cold:     4.24 ms │ Warm:     0.777 ms │ p95:     1.042 ms │   1,235 RPS ║
║ COUNT                        │ Cold:    13.14 ms │ Warm:     2.805 ms │ p95:     3.835 ms │     349 RPS ║
║ COUNT ESTIMATE               │ Cold:     4.17 ms │ Warm:     0.961 ms │ p95:     1.600 ms │     946 RPS ║
║ COUNT CACHED                 │ Cold:     7.94 ms │ Warm:     0.001 ms │ p95:     0.002 ms │ 643,087 RPS ║
║ DELETE (Active Rows)         │ Cold:    22.44 ms │ Warm:     1.120 ms │ p95:     2.018 ms │     790 RPS ║
║ BULK INSERT (100)            │ Cold:     8.30 ms │ Warm:     3.771 ms │ p95:     5.083 ms │     253 RPS ║
║ BULK UPDATE (100 heterogeneous) │ Cold:    21.05 ms │ Warm:     5.993 ms │ p95:     9.341 ms │     157 RPS ║
║ BULK UPDATE (100 homogeneous) │ Cold:     9.29 ms │ Warm:     4.071 ms │ p95:     5.079 ms │     240 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ ACID Transaction Overhead · ⚪ 1.935ms · ↗️ — · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — ACID INTEGRITY AUDIT                                    ║
║                            File: tests/benchmarks/transaction-acid.test.ts                            ║
║                                       Ran: 2026-10-06 09:39:13                                        ║
║         Measures transaction commit latencies and rollback overhead across database adapters          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ TX Commit                    │ Cold:    10.38 ms │ Warm:     0.705 ms │ p95:     0.916 ms │   5,612 RPS ║
║ TX Rollback Integrity        │ Cold:     5.63 ms │ Warm:     1.935 ms │ p95:     2.166 ms │     516 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ System Cache Efficiency · ⚪ 0.750ms · ↗️ — · 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 70% — check connection pool saturation or lock contention. **Severe degradation** (+324%) — review recent commits immediately.

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                            NEGATIVE CACHE PERFORMANCE AUDIT                             ║
║                      File: tests/benchmarks/negative-cache.test.ts                      ║
║                                Ran: 2026-08-23 22:41:20                                 ║
║        Measures Bloom-filter style missing-key cache speedup for repeated misses        ║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ First Miss (DB)                │        2.487 ms │ p95:        4.448 ms │ RPS:        400 ║
║ Cached Miss (Negative Cache)   │        0.001 ms │ p95:        0.002 ms │ RPS:    828,497 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Cache Hit/Miss Ratio & Efficiency · ⚪ 1.321ms · ↗️ — · 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 71% — check connection pool saturation or lock contention. **Severe degradation** (+59%) — review recent commits immediately. > **Check**: `src/databases/cache/redis-adapter.ts` · `src/databases/cache/cache-service.ts`

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — CACHE EFFICIENCY AUDIT                                   ║
║                           File: tests/benchmarks/cache-performance.test.ts                            ║
║                                       Ran: 2026-10-17 15:28:56                                        ║
║         Measures cache hit vs miss latency and efficiency via real HTTP end-to-end requests.          ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Cache Miss (Bypass)          │ Cold:     4.12 ms │ Warm:     0.755 ms │ p95:     0.966 ms │   1,272 RPS ║
║ Cache Hit (L1 Warm)          │ Cold:     0.88 ms │ Warm:     0.189 ms │ p95:     0.267 ms │   5,138 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

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

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

🏷️ Middleware · 🟢 3.063ms · ➡️ ⚪ established at 3.06ms (1 run) (2026-09-30 15:24:48) · source

> ⏳ Pending

🏷️ System · 🟢 0.388ms · ↘️ ⚪ stable at 0.494ms (±0.265ms) (3 runs) (2026-09-18 18:23:47) · source

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

⏳ Pending

🏷️ Metadata · 🟢 0.707ms · ➡️ ⚪ stable at 0.738ms (±0.092ms) (3 runs) (2026-09-18 18:23:48) · source

> ⏳ Pending

🏷️ CRUD · 🟢 4.330ms · ➡️ recorded (awaiting trend) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — LOCALCMS CRUD TAX (POSTGRESQL) ║ ║ File: tests/benchmarks/local-cms-crud.test.ts ║ ║ Ran: 2026-10-06 11:02:17 ║ ║Measures full CollectionsNamespace tax vs direct adapter baseline with isolated garbage collection and deterministic ID generation.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Adapter FIND ONE │ Cold: 4.33 ms │ Warm: 0.495 ms │ p95: 0.751 ms │ 1,877 RPS ║ ║ Direct-to-Wire Point Stream │ Cold: 3.01 ms │ Warm: 0.448 ms │ p95: 0.578 ms │ 2,173 RPS ║ ║ LocalCMS findById (Warm) │ Cold: 0.21 ms │ Warm: 0.001 ms │ p95: 0.003 ms │ 540,760 RPS ║ ║ LocalCMS findById (Cold) │ Cold: 1.74 ms │ Warm: 0.416 ms │ p95: 0.678 ms │ 2,248 RPS ║ ║ LocalCMS create │ Cold: 3.33 ms │ Warm: 0.516 ms │ p95: 0.672 ms │ 1,914 RPS ║ ║ LocalCMS update │ Cold: 6.94 ms │ Warm: 0.560 ms │ p95: 0.716 ms │ 1,743 RPS ║ ║ LocalCMS mixed C/U/R │ Cold: 4.61 ms │ Warm: 1.491 ms │ p95: 1.958 ms │ 646 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Logic · 🟢 ⏳ pending · ➡️ ⚪ established at 0ms (1 run) (2026-10-17 12:06:48) · source

> ⏳ Pending

🏷️ SDK · 🟢 0.008ms · ➡️ ⚪ established at 0.008ms (1 run) (2026-10-17 12:06:48) · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — SDK VS DIRECT ADAPTER (POSTGRESQL) ║ ║ File: tests/benchmarks/local-sdk-vs-direct.test.ts ║ ║ Ran: 2026-10-06 11:02:38 ║ ║Measures the exact SDK tax across Create, Find, and Update pathways with isolated GC sweeps and zero-allocation key pools.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Direct insert │ 0.483 ms │ p95: 0.483 ms │ RPS: 2,072 ║ ║ SDK create (full) │ 1.496 ms │ p95: 1.496 ms │ RPS: 0 ║ ║ Direct findOne │ 0.474 ms │ p95: 0.474 ms │ RPS: 2,111 ║ ║ SDK find (bypassCache) │ 1.476 ms │ p95: 1.476 ms │ RPS: 677 ║ ║ Direct update │ 0.485 ms │ p95: 0.485 ms │ RPS: 2,061 ║ ║ SDK update (full) │ 1.457 ms │ p95: 1.457 ms │ RPS: 0 ║ ║ SDK create (detached) │ 1.572 ms │ p95: 1.572 ms │ RPS: 0 ║ ║ SDK update (detached) │ 1.572 ms │ p95: 1.572 ms │ RPS: 0 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ HTTP · 🟢 0.439ms · ➡️ ⚪ established at 0.439ms (1 run) (2026-10-17 12:06:48) · source

> ⏳ Pending

🏷️ CRUD (Get) · 🟢 0.713ms · ➡️ ⚪ stable at 0.731ms (±0.122ms) (3 runs) (2026-09-18 18:23:48) · source

> ⏳ Pending

🏷️ CRUD (List) · 🟢 0.768ms · ➡️ ⚪ stable at 0.779ms (±0.186ms) (3 runs) (2026-09-18 18:23:49) · source

> ⏳ Pending

🏷️ CRUD (Search) · 🟢 0.745ms · ➡️ ⚪ stable at 0.764ms (±0.137ms) (3 runs) (2026-09-18 18:23:49) · source

> ⏳ Pending

🏷️ HTTP-Cold · 🟢 2.014ms · ➡️ ⚪ established at 2.01ms (1 run) (2026-10-17 12:06:48) · source

> ⏳ Pending

🏷️ COMPETITIVE 9-WORKLOAD REPLICA · ⚪ 0.861ms · ↗️ — · source

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

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                       COMPETITIVE 9-WORKLOAD REPLICA (POSTGRESQL)                       ║
║               File: tests/benchmarks/competitive-workload-replica.test.ts               ║
║                                Ran: 2026-08-26 17:17:14                                 ║
║Measures the exact 9 workloads tested in the external benchmark harness against the local server.║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ findById (Concurrent 8c)       │        2.485 ms │ p95:        3.238 ms │ RPS:      3,049 ║
║ findByIdRandom (Concurrent 8c) │        8.552 ms │ p95:       24.943 ms │ RPS:        913 ║
║ listPlain (Concurrent 8c)      │        2.607 ms │ p95:        5.279 ms │ RPS:      2,943 ║
║ listFilterSort (Concurrent 8c) │        2.932 ms │ p95:        3.816 ms │ RPS:      2,573 ║
║ listLarge (Concurrent 8c)      │        2.517 ms │ p95:        3.550 ms │ RPS:      3,041 ║
║ findMissing (Concurrent 8c)    │        2.532 ms │ p95:        6.246 ms │ RPS:      3,041 ║
║ GraphQL Collection Query (Concurrent 8c) │        5.014 ms │ p95:        7.447 ms │ RPS:      1,561 ║
║ create (Concurrent 8c)         │        8.319 ms │ p95:       11.209 ms │ RPS:        921 ║
║ update (Concurrent 8c)         │        9.056 ms │ p95:       13.321 ms │ RPS:        859 ║
║ mixed (Concurrent 8c 50/50)    │        7.491 ms │ p95:       10.122 ms │ RPS:      1,007 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ MIDDLEWARE FLAMEGRAPH PROFILER · ⚪ 1.432ms · ↗️ — · 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 57% — check connection pool saturation or lock contention. **Severe degradation** (+110%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                              MIDDLEWARE FLAMEGRAPH PROFILER (POSTGRESQL)                              ║
║                         File: tests/benchmarks/middleware-flamegraph.test.ts                          ║
║                                       Ran: 2026-10-06 09:42:35                                        ║
║Measures isolated microsecond cost and incremental deltas of each middleware stage from edge to database.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Stage 0: Raw Socket Baseline (Static Asset) │ Cold:     2.65 ms │ Warm:     0.794 ms │ p95:     1.320 ms │   4,757 RPS ║
║ Stage 1: System State + Turbo Pipeline │ Cold:     1.16 ms │ Warm:     0.681 ms │ p95:     1.044 ms │   5,566 RPS ║
║ Stage 2: WAF Security Inspection │ Cold:     0.90 ms │ Warm:     0.592 ms │ p95:     1.040 ms │   5,768 RPS ║
║ Stage 3: Token Auth Gating   │ Cold:     6.92 ms │ Warm:     1.501 ms │ p95:     2.048 ms │   2,616 RPS ║
║ Stage 4: Collection Schema Resolution │ Cold:     6.59 ms │ Warm:     0.341 ms │ p95:     0.669 ms │  10,702 RPS ║
║ Stage 5: Full REST Single Document │ Cold:     4.23 ms │ Warm:     0.293 ms │ p95:     0.528 ms │  12,425 RPS ║
║ Stage 6: GraphQL Single Query (JIT) │ Cold:     3.15 ms │ Warm:     1.432 ms │ p95:     1.871 ms │   2,706 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ EVENT LOOP LAG & SATURATION · ⚪ ⏳ pending · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ EVENT LOOP LAG & SATURATION (POSTGRESQL) ║ ║ File: tests/benchmarks/event-loop-lag.test.ts ║ ║ Ran: 2026-10-06 11:01:59 ║ ║Measures event loop delay (p50, p95, p99, max) and microtask drain speed under concurrent write bursts.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Idle Baseline Lag │ 0.000 ms │ p95: 0.000 ms │ RPS: 1,182 ║ ║ Write Burst Lag (200 writes @ 16c) │ 0.000 ms │ p95: 0.000 ms │ RPS: 962 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Ingestion · 🟢 0.203ms · ➡️ ⚪ established at 0.203ms (1 run) (2026-10-15 16:05:02) · source

> ⏳ Pending

🏷️ DB · 🟢 0.543ms · ➡️ ⚪ established at 0.543ms (1 run) (2026-09-26 23:02:36) · source

> ⏳ Pending

API · 9 tests

🏷️ Temporal Integrity Audit · ⚪ 2.923ms · ➡️ — · source

``` ╔═════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — TEMPORAL INTEGRITY ║ ║ File: tests/benchmarks/temporal-integrity.test.ts ║ ║ Ran: 2026-08-23 22:08:48 ║ ║Validates deterministic UTC normalization of ISO date strings across timezone offsets for consistent persistence.║ ╠═════════════════════════════════════════════════════════════════════════════════════════╣ ║ Timezone Ingestion │ 4.762 ms │ p95: 4.762 ms │ RPS: 210 ║ ╚═════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Relational & Nested Queries · ⚪ ⏳ pending · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — RELATIONAL RESOLVER AUDIT ║ ║ File: tests/benchmarks/relational-performance.test.ts ║ ║ Ran: 2026-08-29 20:57:20 ║ ║Measures GraphQL resolver performance for shallow listings, deep relational joins, and nested author population across cold/hot execution paths.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Shallow Query (Collections) │ Cold: 2.87 ms │ Warm: 2.707 ms │ p95: 4.494 ms │ 2,064 RPS ║ ║ Deep Join (Cold DB) │ Cold: 3.14 ms │ Warm: 2.225 ms │ p95: 3.868 ms │ 1,645 RPS ║ ║ Deep Join (Warm Cached) │ Cold: 1.63 ms │ Warm: 1.765 ms │ p95: 2.902 ms │ 2,049 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Auth & RBAC Performance · ⚪ 1.122ms · ↗️ — · source

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — AUTHENTICATION TELEMETRY                                  ║
║                            File: tests/benchmarks/auth-performance.test.ts                            ║
║                                       Ran: 2026-10-06 10:55:29                                        ║
║           Evaluates authenticated session resolution, RBAC evaluation, and rejection paths.           ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Unauthenticated (401 reject) │ Cold:     2.49 ms │ Warm:     0.810 ms │ p95:     0.989 ms │   1,213 RPS ║
║ Reject: unknown session cookie │ Cold:     0.99 ms │ Warm:     0.893 ms │ p95:     1.067 ms │   1,095 RPS ║
║ Reject: unknown API key (Bearer sck_) │ Cold:     1.13 ms │ Warm:     0.832 ms │ p95:     1.032 ms │   1,176 RPS ║
║ Auth Validation @ 1c         │ Cold:     2.26 ms │ Warm:     0.734 ms │ p95:     1.066 ms │   1,286 RPS ║
║ HTTP Auth Pipeline @ 8c      │ Cold:     2.93 ms │ Warm:     1.929 ms │ p95:     2.379 ms │   4,034 RPS ║
║ Auth (full chain) @ 1c       │ Cold:     2.07 ms │ Warm:     0.358 ms │ p95:     0.553 ms │   2,596 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ REST API Performance · ⚪ 0.859ms · ↗️ — · 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** (+68%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — ENTERPRISE REST API AUDIT                                 ║
║                          File: tests/benchmarks/rest-api-performance.test.ts                          ║
║                                       Ran: 2026-10-06 09:35:45                                        ║
║Measures latency, throughput, and correctness of core REST endpoints: health check, schema, single read, list, and search.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ System Health Check          │ Cold:     1.53 ms │ Warm:     0.859 ms │ p95:     1.391 ms │   4,454 RPS ║
║ Collection Schema Metadata   │ Cold:     6.07 ms │ Warm:     0.424 ms │ p95:     0.871 ms │   8,132 RPS ║
║ Single Document Read         │ Cold:     2.30 ms │ Warm:     0.425 ms │ p95:     0.817 ms │   8,249 RPS ║
║ Collection Find (List Limit 20) │ Cold:     8.54 ms │ Warm:     0.581 ms │ p95:     0.888 ms │   6,069 RPS ║
║ Collection Search Query      │ Cold:     3.05 ms │ Warm:     0.527 ms │ p95:     0.914 ms │   6,621 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ GraphQL API Performance · ⚪ 0.724ms · ↘️ — · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective. Throughput dropped 51% — check connection pool saturation or lock contention.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — GRAPHQL CACHE HIT AUDIT                                  ║
║                           File: tests/benchmarks/graphql-cache-hit.test.ts                            ║
║                                       Ran: 2026-10-06 09:41:56                                        ║
║        Validates sub-millisecond L1 response cache hits, cache key isolation, and hit headers.        ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Q1: Health (Cold Miss)         │        4.110 ms │ p95:        4.110 ms │ RPS:        243 ║
║ Q1: Health (L1 Hit)            │        0.995 ms │ p95:        1.225 ms │ RPS:      1,005 ║
║ Q2: Collections (Cold Miss)    │        1.729 ms │ p95:        1.729 ms │ RPS:        578 ║
║ Q2: Collections (L1 Hit)       │        1.002 ms │ p95:        1.518 ms │ RPS:        998 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Enterprise SEO Suite Audit · ⚪ ⏳ pending · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — ENTERPRISE SEO AUDIT ║ ║ File: tests/benchmarks/seo-performance.test.ts ║ ║ Ran: 2026-08-29 20:57:26 ║ ║Measures redirect lookup latency, dynamic sitemap.xml generation, robots.txt serving, and 404 logging performance.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Redirect Lookup (301) │ Cold: 1.17 ms │ Warm: 1.525 ms │ p95: 2.626 ms │ 5,187 RPS ║ ║ Dynamic Sitemap XML │ Cold: 18.70 ms │ Warm: 0.924 ms │ p95: 1.533 ms │ 8,591 RPS ║ ║ Robots.txt Generation │ Cold: 2.15 ms │ Warm: 1.733 ms │ p95: 2.857 ms │ 4,586 RPS ║ ║ Missing Path (404 Log) │ Cold: 59.89 ms │ Warm: 17.365 ms │ p95: 24.798 ms │ 457 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ REAL-TIME BROADCAST AUDIT · ⚪ 0.142ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — YJS COLLABORATION SYNC AUDIT ║ ║ File: tests/benchmarks/websocket-broadcast.test.ts ║ ║ Ran: 2026-10-06 11:01:02 ║ ║Measures WebSocket handshake latency, bidirectional Yjs CRDT update propagation, and synchronization throughput.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ WS Handshake + SyncStep │ 6.870 ms │ p95: 0.000 ms │ RPS: 0 ║ ║ Yjs CRDT Propagation │ Cold: 2.27 ms │ Warm: 0.213 ms │ p95: 0.517 ms │ 3,899 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ WebSocket & Realtime Latency · ⚪ ⏳ pending · ➡️ — · source

> ⏳ **WebSocket & Realtime Latency**: Pending execution. > 🎯 Benchmarks WebSocket connection/broadcast latency.

🏷️ GraphQL Response Cache Hit · ⚪ 1.002ms · ↘️ — · source

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — GRAPHQL CACHE HIT AUDIT                                  ║
║                           File: tests/benchmarks/graphql-cache-hit.test.ts                            ║
║                                       Ran: 2026-10-06 11:02:01                                        ║
║        Validates sub-millisecond L1 response cache hits, cache key isolation, and hit headers.        ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Q1: Health (Cold Miss)         │        5.163 ms │ p95:        5.163 ms │ RPS:        194 ║
║ Q1: Health (L1 Hit)            │        1.080 ms │ p95:        1.590 ms │ RPS:        926 ║
║ Q2: Collections (Cold Miss)    │        2.062 ms │ p95:        2.062 ms │ RPS:        485 ║
║ Q2: Collections (L1 Hit)       │        0.985 ms │ p95:        1.288 ms │ RPS:      1,015 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

Scale · 18 tests

🏷️ Negative Cache Performance · ⚪ 0.001ms · ↘️ — · source

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

╔═════════════════════════════════════════════════════════════════════════════════════════╗
║                            NEGATIVE CACHE PERFORMANCE AUDIT                             ║
║                      File: tests/benchmarks/negative-cache.test.ts                      ║
║                                Ran: 2026-08-23 22:41:20                                 ║
║        Measures Bloom-filter style missing-key cache speedup for repeated misses        ║
╠═════════════════════════════════════════════════════════════════════════════════════════╣
║ First Miss (DB)                │        2.487 ms │ p95:        4.448 ms │ RPS:        400 ║
║ Cached Miss (Negative Cache)   │        0.001 ms │ p95:        0.002 ms │ RPS:    828,497 ║
╚═════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Revision & History Growth · ⚪ 0.446ms · ↘️ — · 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-10-06 09:37:59                                        ║
║Measures latest read degradation, history retrieval speed, and storage footprint under heavy revision growth (100 revisions).║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Clean Document Read (Baseline) │ Cold:     3.26 ms │ Warm:     0.525 ms │ p95:     0.772 ms │   7,275 RPS ║
║ Latest Read (100 Revisions)  │ Cold:     3.37 ms │ Warm:     0.446 ms │ p95:     0.768 ms │   8,386 RPS ║
║ History List Retrieval       │ Cold:     6.29 ms │ Warm:     1.498 ms │ p95:     1.953 ms │   1,280 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

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

> ⏳ **Memory Stability & GC Behavior**: Pending execution. > 🎯 Long-running soak test to identify memory leaks and GC pressure.

🏷️ Multi-Tenant Performance & Isolation · ⚪ 0.826ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — MULTI-TENANCY PERFORMANCE AUDIT ║ ║ File: tests/benchmarks/multi-tenant-performance.test.ts ║ ║ Ran: 2026-10-06 09:36:27 ║ ║Measures the overhead of tenant isolation, context switching, and data partitioning across many tenants.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Single Tenant Baseline │ Cold: 4.88 ms │ Warm: 0.918 ms │ p95: 1.259 ms │ 8,376 RPS ║ ║ Multi-Tenant Context Switching │ Cold: 0.87 ms │ Warm: 0.826 ms │ p95: 1.211 ms │ 8,957 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Realistic Mixed Workload · ⚪ 0.798ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — MIXED WORKLOAD AUDIT ║ ║ File: tests/benchmarks/mixed-workload.test.ts ║ ║ Ran: 2026-10-06 09:36:45 ║ ║Simulates real-world traffic with a weighted mix of reads, searches, GraphQL queries, and metadata requests with per-operation telemetry.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Mixed Workload │ Cold: 8.29 ms │ Warm: 0.798 ms │ p95: 2.513 ms │ 7,418 RPS ║ ║ Mix: REST Read │ 0.955 ms │ p95: 1.810 ms │ RPS: 1,942 ║ ║ Mix: REST Search │ 1.001 ms │ p95: 1.830 ms │ RPS: 636 ║ ║ Mix: GraphQL │ 2.695 ms │ p95: 4.807 ms │ RPS: 493 ║ ║ Mix: Metadata │ 0.992 ms │ p95: 1.740 ms │ RPS: 172 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ GraphQL Load Stress · ⚪ 10.161ms · ↗️ — · source

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                SVELTYCMS — GRAPHQL CAPACITY DISCOVERY                                 ║
║                             File: tests/benchmarks/graphql-stress.test.ts                             ║
║                                       Ran: 2026-10-06 10:55:40                                        ║
║                Discovers maximum sustainable GraphQL throughput by ramping concurrency                ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ GQL: 5c Warmup               │ Cold:     2.53 ms │ Warm:     1.334 ms │ p95:     2.161 ms │   3,531 RPS ║
║ GQL: 10c Light               │ Cold:     2.24 ms │ Warm:     2.056 ms │ p95:     2.595 ms │   4,740 RPS ║
║ GQL: 20c Moderate            │ Cold:     2.91 ms │ Warm:     4.099 ms │ p95:     7.955 ms │   4,126 RPS ║
║ GQL: 40c Heavy               │ Cold:     2.43 ms │ Warm:     5.660 ms │ p95:     9.026 ms │   6,711 RPS ║
║ GQL: 60c Stress              │ Cold:     1.71 ms │ Warm:     6.906 ms │ p95:    10.754 ms │   8,111 RPS ║
║ GQL: 80c Extreme             │ Cold:     2.15 ms │ Warm:    12.039 ms │ p95:    24.008 ms │   6,059 RPS ║
║ GQL: 100c Max                │ Cold:     1.82 ms │ Warm:    15.209 ms │ p95:    22.688 ms │   6,434 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Bulk Migration & Scale · ⚪ ⏳ pending · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — MIGRATION & SCALE AUDIT ║ ║ File: tests/benchmarks/migration-scale.test.ts ║ ║ Ran: 2026-08-29 21:01:33 ║ ║Measures bulk ingestion throughput for 10,000 entries, random point-lookups, and indexed range scans across large datasets.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Bulk Migration (10k docs) │ Cold: 123.65 ms │ Warm: 25.910 ms │ p95: 57.352 ms │ 14,636 RPS ║ ║ Random Point Lookup │ Cold: 9.01 ms │ Warm: 4.645 ms │ p95: 8.035 ms │ 1,226 RPS ║ ║ Range Scan & Pagination │ Cold: 26.17 ms │ Warm: 1.210 ms │ p95: 1.879 ms │ 4,642 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Million-Row Index Pressure · ⚪ 0.837ms · ↗️ — · source

> [!NOTE] > **Specific to this test**: Both avg and p95 degraded — likely adapter or infrastructure bottleneck. Check DB connection pool, indexes, or recent commits.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS  —  INDEX PRESSURE AUDIT                                   ║
║                             File: tests/benchmarks/index-pressure.test.ts                             ║
║                                       Ran: 2026-10-06 09:37:49                                        ║
║           Measures read performance with sorting and filtering on a large entry collection.           ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Sorted List (25k rows)       │ Cold:     6.28 ms │ Warm:     0.837 ms │ p95:     1.382 ms │   4,722 RPS ║
║ Filtered Query (25k rows)    │ Cold:     4.26 ms │ Warm:     0.796 ms │ p95:     1.513 ms │   4,988 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Content Scale Stress · ⚪ 0.134ms · ↘️ — · source

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                SVELTYCMS — CONTENT SCALE STRESS AUDIT                                 ║
║                          File: tests/benchmarks/content-scale-stress.test.ts                          ║
║                                       Ran: 2026-10-06 10:59:15                                        ║
║        Measures file-scanning and content discovery performance at scale (1,000+ collections).        ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Cold Stress Scan (1000 files)  │        0.752 ms │ p95:        0.856 ms │ RPS:      1,329 ║
║ Warm Stress Scan (1000 files) │ Cold:     0.46 ms │ Warm:     0.151 ms │ p95:     0.208 ms │   6,229 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Media Upload Stress & Throughput · ⚪ 5.908ms · ↘️ — · source

> [!NOTE] > **Specific to this test**: Performance improved — recent optimizations or cache warming likely effective. > **Check**: `src/services/MediaService.ts` · `src/databases/media/`

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — MEDIA UPLOAD STRESS AUDIT                                 ║
║                          File: tests/benchmarks/media-upload-stress.test.ts                           ║
║                                       Ran: 2026-10-06 09:40:09                                        ║
║Measures throughput for large file uploads, concurrent transfers, and streaming efficiency with valid media fixtures.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Single Upload (0.01MB)       │ Cold:     8.75 ms │ Warm:     5.079 ms │ p95:     5.436 ms │     197 RPS ║
║ Small Upload (0MB @ 4c)      │ Cold:     8.76 ms │ Warm:     5.908 ms │ p95:     8.632 ms │     650 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Full Client Journey Simulation · ⚪ 5.719ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — WORLD LIFE DATA ║ ║ File: tests/benchmarks/client-journey.test.ts ║ ║ Ran: 2026-10-06 10:57:12 ║ ║ Measures cumulative latency of a realistic editorial user workflow: Auth → List → View → Edit → Save. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Full Journey @ 1c │ Cold: 19.89 ms │ Warm: 5.366 ms │ p95: 6.212 ms │ 186 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Concurrency & Race Condition · ⚪ ⏳ pending · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — CONCURRENCY AUDIT ║ ║ File: tests/benchmarks/concurrency-race.test.ts ║ ║ Ran: 2026-10-06 09:40:27 ║ ║ Simulates high-concurrency writes to a single document to prove atomic consistency. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Concurrent PATCH Bomb │ 13.318 ms │ p95: 19.669 ms │ RPS: 1,807 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

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

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — DIRECT ADAPTER THROUGHPUT (POSTGRESQL) ║ ║ File: tests/benchmarks/local-api-throughput.test.ts ║ ║ Ran: 2026-10-06 09:38:00 ║ ║Measures direct adapter write throughput, read throughput, and percentile latencies with zero HTTP overhead.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Writes (1000 atomic increments) │ 1.620 ms │ p95: 2.280 ms │ RPS: 4,952 ║ ║ Reads (1000 point lookups) │ 1.375 ms │ p95: 2.590 ms │ RPS: 9,273 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Max Throughput — No Throttle · ⚪ 22.034ms · ➡️ — · source

> ⏳ **Max Throughput — No Throttle**: Pending execution. > 🎯 1000 concurrent writes across 100 docs — no semaphore.

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

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — AI INFRASTRUCTURE AUDIT ║ ║ File: tests/benchmarks/ai-performance.test.ts ║ ║ Ran: 2026-10-06 10:56:49 ║ ║ Measures the latency tax of internal CMS logic for AI enrichment and layout generation. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ AI Text Enrichment │ Cold: 0.05 ms │ Warm: 0.000 ms │ p95: 0.001 ms │ 1,372,998 RPS ║ ║ AI Layout Spec Generation │ Cold: 0.03 ms │ Warm: 0.000 ms │ p95: 0.001 ms │ 1,312,336 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Chaos & Infrastructure Resilience · ⚪ ⏳ pending · ➡️ — · source

``` ╔═════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — CHAOS RESILIENCE AUDIT ║ ║ File: tests/benchmarks/chaos-resilience.test.ts ║ ║ Ran: 2026-07-21 16:16:17 ║ ║Simulates infrastructure brownouts and measures system stability and graceful degradation under stress.║ ╠═════════════════════════════════════════════════════════════════════════════════════════╣ ║ Chaos Resilience (Brownout) │ 170.556 ms │ p95: 686.820 ms │ RPS: 6 ║ ╚═════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Production Day Simulation · ⚪ 1.799ms · ➡️ — · source

> ⏳ **Production Day Simulation**: Pending execution. > 🎯 Full production day with mixed workload, 100% reliability.

Resilience · 5 tests

🏷️ Circuit Breaker Failover · ⚪ ⏳ pending · ➡️ — · source

> ⏳ **Circuit Breaker Failover**: Pending execution. > 🎯 Measures system graceful degradation when external services fail.

🏷️ Throttling & Backoff Stress · ⚪ ⏳ pending · ➡️ — · source

``` ╔═════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — THROTTLING AUDIT ║ ║ File: tests/benchmarks/throttling-backoff-stress.test.ts ║ ║ Ran: 2026-07-21 16:20:21 ║ ║Simulates high-velocity traffic from a single client IP to verify rate-limiting enforcement and backoff consistency.║ ╠═════════════════════════════════════════════════════════════════════════════════════════╣ ║ Throttling Enforcement │ 2.568 ms │ p95: 5.015 ms │ RPS: 389 ║ ╚═════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Data Residency & Sovereignty · ⚪ ⏳ pending · ➡️ — · source

> ⏳ **Data Residency & Sovereignty**: Pending execution. > 🎯 PII blocking and data sovereignty enforcement with cross-region failover.

🏷️ Database Failover & Reconnection · ⚪ ⏳ pending · ➡️ — · source

``` ╔═════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — DATABASE FAILOVER AUDIT ║ ║ File: tests/benchmarks/database-failover.test.ts ║ ║ Ran: 2026-07-21 16:20:14 ║ ║ Simulates database connection loss mid-request and measures circuit breaker activation, ║ ╠═════════════════════════════════════════════════════════════════════════════════════════╣ ║ Baseline Health Check │ 0.247 ms │ p95: 0.342 ms │ RPS: 4,054 ║ ║ Degraded Dependency │ 0.595 ms │ p95: 0.951 ms │ RPS: 1,680 ║ ║ Post-Recovery Health │ 2.168 ms │ p95: 3.147 ms │ RPS: 461 ║ ║ Reconnect Time │ 0.424 ms │ p95: 0.424 ms │ RPS: 0 ║ ╚═════════════════════════════════════════════════════════════════════════════════════════╝ ```

🔬 Host environment

Host	Platform	Arch	Cores	RAM	Runtime
RKroells	win32	x64	24	63GB	Bun 1.4.2