MariaDB + Redis Performance Audit

Database performance benchmarks with trend analysis and competitive context.

7/4/2026

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

📊 Latest Performance Audit

📝 Fix Overlays

Note

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

(06/10/2026, 12:54:58)

✅ PASS · 23/45 tests · 22 skipped · MARIADB+REDIS · Bun 1.4.2

Dimension health

Dimension	Tests	Status	Worst Δ
Core	13	🟢	+514%
API	9	🟢	-60%
Scale	18	🟢	+165%
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 "MARIADB+REDIS 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.23, 0.95] COMPETITIVE 9-WORKLOAD REPLI: [0.09, 0.09] MIDDLEWARE FLAMEGRAPH PROFIL: [0.09, 0.22] Incremental Content Reload: [0.05, 0.45] Middleware & Hooks Performan: [0.05, 0.05] Database Adapter Raw CRUD: [0.05, 0.08] REST API Performance: [0.05, 0.07] GraphQL API Performance: [0.06, 0.09]

Current Run Summary

Only tests that ran in THIS invocation. Populated after BENCHMARK_RECORD=1 or matrix run.

Historical Trends (2026-10-06)

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='mariadb' AND redis=1 ORDER BY timestamp DESC

Series: 55 · DB: mariadb-redis

Metric	Trend	Sparkline (last 7)	Latest
ADMIN UX VITALITY (warm)	🟢	`█▁`	0.524ms
AI PERFORMANCE (warm)	🟢	`▁▁`	0.000ms
API LATENCY (warm)	🟢	`▆▂▁▁█`	3.604ms
AUTH PERFORMANCE (warm)	🟢	`▁▃█▃▃▃`	0.874ms
AUTH SESSION AMR (warm)	🟢	`▄▇█▁`	0.431ms
BUILD ANALYSIS (warm)	🟢	`▁`	0.000ms
CACHE HIT RATIO (warm)	🟢	`▄▄▁█`	1.781ms
CACHE PERFORMANCE (warm)	🟢	`▁█`	0.803ms
CACHE SERVICE (warm)	🟢	`▁▇█`	0.596ms
CLIENT JOURNEY (warm)	🟢	`▁`	5.861ms
COMPETITIVE WORKLOAD REPLICA (warm)	🟢	`▁▂▁▅▂█▃`	1.435ms
CONCURRENCY MAX (warm)	🟢	`▁`	28.764ms
CONTENT GUI SAVE (warm)	🟢	`▁`	1.561ms
CONTENT SCALE STRESS (warm)	🟢	`█▁`	0.135ms
CONTENT SCAN (warm)	🟢	`█▁`	0.660ms
DATABASE PERFORMANCE (warm)	🟢	`▂▁▂▁█▂▁`	0.396ms
EDGE SYNC (warm)	🟢	`▁`	2.674ms
ENTRY EDIT HYDRATION (warm)	🟢	`█▁▁▅`	0.015ms
GRAPHQL CACHE HIT (warm)	🟢	`█▁▆▁`	1.073ms
GRAPHQL LOCAL SDK (warm)	🟢	`█▁`	0.000ms
GRAPHQL STRESS (warm)	🟢	`█▁▂▃▁▅▇`	15.753ms
HOOKS PERFORMANCE (warm)	🟢	`▁█▁▃▃`	0.748ms
INDEX PRESSURE (warm)	🟢	`▁█`	0.704ms
LARGE PAYLOAD STREAMING (warm)	🟢	`▁█▁▇`	9.938ms
LOCAL API THROUGHPUT (warm)	🟢	`█▁`	1.093ms
MEDIA UPLOAD STRESS (warm)	🟢	`▁█`	9.393ms
MEMORY COUNTERS (warm)	🟢	`▁`	0.000ms
MIGRATION SCALE (warm)	🟢	`█▂▁`	0.501ms
MIXED WORKLOAD (warm)	🟢	`▁`	0.765ms
MULTI TENANT PERFORMANCE (warm)	🟢	`▁`	1.069ms
OPENAPI PERFORMANCE (warm)	🟢	`▇▁█`	2.110ms
PRODUCTION DAY (warm)	🟢	`▁`	2.373ms
REALTIME PERFORMANCE (warm)	🟢	`▁▁▁`	0.000ms
REVISION STRESS (warm)	🟢	`▁█▁`	0.349ms
RIGHT TO BE FORGOTTEN AUDIT (warm)	🟢	`▁`	8.030ms
SCALE SPECTRUM (warm)	🟢	`▃▇▇▇█▁█`	1.004ms
SECURITY AUDIT (warm)	🟢	`▁█▁█▁██`	0.001ms
SEO PERFORMANCE (warm)	🟢	`▁█▁▁`	1.568ms
SHARP VS BUN IMAGE (warm)	🟢	`▇▄▁▂▁██`	60.996ms
STATE MACHINE TRANSITION (warm)	🟢	`▁█`	52.614ms
TELEMETRY PERFORMANCE (warm)	🟢	`█▁`	0.000ms
TEMPORAL INTEGRITY (warm)	🟢	`▁`	3.683ms
TRANSACTION ACID (warm)	🟢	`▁█`	1.846ms
TRUTH LATENCY (warm)	🟢	`█▃▁▁`	0.000ms
WEBSOCKET BROADCAST (warm)	🟢	`▁`	0.108ms
WIDGET PERFORMANCE (warm)	🟢	`█▁▇`	0.555ms
CONFIG PROMOTION (warm)	⚪	`▅▅█▅▁▂`	9.038ms
CONTENT INCREMENTAL RELOAD (warm)	⚪	`▃▃▁█`	0.690ms
GRAPHQL API PERFORMANCE (warm)	⚪	`▅▄█▅▁▁`	0.933ms
LOCAL API PERFORMANCE (warm)	⚪	`▆█▁`	0.337ms
LOCAL CMS CRUD (warm)	⚪	`▃▃▃▂▁█▄`	0.944ms
LOCAL SDK VS DIRECT (warm)	⚪	`▂▄▁▂▅██`	1.308ms
MIDDLEWARE FLAMEGRAPH (warm)	⚪	`▄▃▃█▁▁▇`	1.355ms
NEGATIVE CACHE (warm)	⚪	`██▁`	0.001ms
REST API PERFORMANCE (warm)	⚪	`▄▃▆▁█`	0.728ms

📊 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 · 13 tests

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

⏳ API LAYER LATENCY: Pending execution. 🎯 Measures the base network and HTTP overhead for the simplest possible API calls.

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

> ⏳ **PHASED COLD START**: Pending execution. > 🎯 Measures the time to READY state (serving traffic) vs WARMED state (background tasks).

🏷️ 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-06 10:46:25                                        ║
║            Validates performance claims by comparing SDK, Middleware, and Real HTTP Stack             ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Logic Baseline               │ Cold:     0.03 ms │ Warm:     0.000 ms │ p95:     0.000 ms │ 555,453 RPS ║
║ Local SDK (Full)             │ Cold:    16.04 ms │ Warm:     0.006 ms │ p95:     0.010 ms │ 154,115 RPS ║
║ HTTP End-to-End              │ Cold:    11.84 ms │ Warm:     0.271 ms │ p95:     0.347 ms │   3,655 RPS ║
║ HTTP Cold (Cache-Busted)     │ Cold:     2.26 ms │ Warm:     0.993 ms │ p95:     1.410 ms │   1,005 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Incremental Content Reload · ⚪ 0.690ms · ↗️ — · 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 80% — check connection pool saturation or lock contention. **Severe degradation** (+230%) — 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 10:50:28                                        ║
║      Measures surgical single-file fullReload vs full reconciliation path and batch processing.       ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Incremental fullReload (1 file) │ Cold:     4.43 ms │ Warm:     0.065 ms │ p95:     0.184 ms │  12,828 RPS ║
║ Full Reconciliation Reload   │ Cold:     2.67 ms │ Warm:     0.209 ms │ p95:     0.273 ms │   4,593 RPS ║
║ Sequential 10-File Reload    │ Cold:     4.38 ms │ Warm:     0.690 ms │ p95:     1.096 ms │   1,442 RPS ║
║ Batched 10-File Reload       │ Cold:     0.89 ms │ Warm:     0.238 ms │ p95:     0.366 ms │   3,722 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Middleware & Hooks Performance · ⚪ 0.748ms · ↗️ — · source

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

⏳ Middleware & Hooks Performance: Pending execution. 🎯 High-resolution micro-benchmarks (µs) for individual middleware layers.

🏷️ State Machine Transitions · ⚪ 52.614ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — STATE MACHINE INTEGRITY ║ ║ File: tests/benchmarks/state-machine-transition.test.ts ║ ║ Ran: 2026-10-06 10:50:36 ║ ║Measures state machine self-healing transition latencies, convergence settling time, and health probe consistency under stress.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ State Transition (Transient) │ Cold: 84.01 ms │ Warm: 52.614 ms │ p95: 65.705 ms │ 19 RPS ║ ║ Self-Healing Full Convergence │ Cold: 51.36 ms │ Warm: 49.148 ms │ p95: 57.796 ms │ 20 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Database Adapter Raw CRUD · ⚪ 0.396ms · ↘️ — · source

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

⏳ Database Adapter Raw CRUD: Pending execution. 🎯 Direct low-level benchmarks of Create, Read, Update, Delete on the current database adapter.

🏷️ ACID Transaction Overhead · ⚪ 1.846ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — ACID INTEGRITY AUDIT ║ ║ File: tests/benchmarks/transaction-acid.test.ts ║ ║ Ran: 2026-10-06 10:50:11 ║ ║ Measures transaction commit latencies and rollback overhead across database adapters ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ TX Commit │ Cold: 2.52 ms │ Warm: 0.745 ms │ p95: 1.371 ms │ 4,968 RPS ║ ║ TX Rollback Integrity │ Cold: 4.65 ms │ Warm: 1.846 ms │ p95: 2.373 ms │ 541 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ System Cache Efficiency · ⚪ 0.803ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — CACHE EFFICIENCY AUDIT ║ ║ File: tests/benchmarks/cache-hit-ratio.test.ts ║ ║ Ran: 2026-10-06 10:47:09 ║ ║ Measures true cold-fill, warm hit ratio, miss penalty, and invalidation latency. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Cache Cold Fill (Miss + Repopulate) │ 0.937 ms │ p95: 1.138 ms │ RPS: 1,067 ║ ║ Cache Hit (Warm) │ Cold: 0.27 ms │ Warm: 0.159 ms │ p95: 0.245 ms │ 6,092 RPS ║ ║ Bypass Cache (Direct DB) │ Cold: 1.03 ms │ Warm: 0.796 ms │ p95: 1.100 ms │ 1,252 RPS ║ ║ Cache Invalidation │ Cold: 3.15 ms │ Warm: 1.781 ms │ p95: 2.089 ms │ 555 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Cache Hit/Miss Ratio & Efficiency · ⚪ 1.781ms · ↗️ — · 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 80% — check connection pool saturation or lock contention. **Severe degradation** (+124%) — 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-hit-ratio.test.ts                             ║
║                                       Ran: 2026-10-06 10:47:09                                        ║
║           Measures true cold-fill, warm hit ratio, miss penalty, and invalidation latency.            ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Cache Cold Fill (Miss + Repopulate) │        0.937 ms │ p95:        1.138 ms │ RPS:      1,067 ║
║ Cache Hit (Warm)             │ Cold:     0.27 ms │ Warm:     0.159 ms │ p95:     0.245 ms │   6,092 RPS ║
║ Bypass Cache (Direct DB)     │ Cold:     1.03 ms │ Warm:     0.796 ms │ p95:     1.100 ms │   1,252 RPS ║
║ Cache Invalidation           │ Cold:     3.15 ms │ Warm:     1.781 ms │ p95:     2.089 ms │     555 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

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

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                    COMPETITIVE HARNESS REPLICA (MARIADB — 500 Docs, COLD vs WARM)                     ║
║                      File: tests/benchmarks/competitive-workload-replica.test.ts                      ║
║                                       Ran: 2026-10-06 10:53:01                                        ║
║              Seq + concurrent (8 workers), harness iteration counts, median of N rounds.              ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ findById (Cold Sequential)   │ Cold:     4.62 ms │ Warm:     0.587 ms │ p95:     1.144 ms │   1,678 RPS ║
║ findById (Cold Concurrent 8c) │ Cold:     0.99 ms │ Warm:     2.132 ms │ p95:     3.068 ms │   3,634 RPS ║
║ findByIdRandom (Cold Sequential) │ Cold:     4.58 ms │ Warm:     1.059 ms │ p95:     1.593 ms │     942 RPS ║
║ findByIdRandom (Cold Concurrent 8c) │ Cold:     2.99 ms │ Warm:     3.106 ms │ p95:     4.237 ms │   2,512 RPS ║
║ listFilterSort (Cold Sequential) │ Cold:     4.60 ms │ Warm:     0.400 ms │ p95:     0.508 ms │   2,488 RPS ║
║ listFilterSort (Cold Concurrent 8c) │ Cold:     0.45 ms │ Warm:     2.168 ms │ p95:     3.805 ms │   3,510 RPS ║
║ listLarge (Cold Sequential)  │ Cold:     5.13 ms │ Warm:     0.489 ms │ p95:     0.690 ms │   2,034 RPS ║
║ listLarge (Cold Concurrent 8c) │ Cold:     0.38 ms │ Warm:     1.467 ms │ p95:     2.417 ms │   5,284 RPS ║
║ listPlain (Cold Sequential)  │ Cold:     2.64 ms │ Warm:     0.278 ms │ p95:     0.347 ms │   3,578 RPS ║
║ listPlain (Cold Concurrent 8c) │ Cold:     0.32 ms │ Warm:     1.109 ms │ p95:     1.535 ms │   6,981 RPS ║
║ findMissing (Cold Sequential) │ Cold:     4.84 ms │ Warm:     0.281 ms │ p95:     0.292 ms │   3,550 RPS ║
║ findMissing (Cold Concurrent 8c) │ Cold:     0.24 ms │ Warm:     0.875 ms │ p95:     1.035 ms │   8,799 RPS ║
║ create (Cold Sequential)     │ Cold:     5.07 ms │ Warm:     1.449 ms │ p95:     1.979 ms │     689 RPS ║
║ create (Cold Concurrent 8c)  │ Cold:     4.81 ms │ Warm:     7.036 ms │ p95:     9.594 ms │   1,118 RPS ║
║ update (Cold Sequential)     │ Cold:     3.25 ms │ Warm:     1.459 ms │ p95:     1.885 ms │     685 RPS ║
║ update (Cold Concurrent 8c)  │ Cold:     4.37 ms │ Warm:     6.261 ms │ p95:     9.034 ms │   1,251 RPS ║
║ graphql (Cold Sequential)    │ Cold:     4.92 ms │ Warm:     1.021 ms │ p95:     1.530 ms │     978 RPS ║
║ graphql (Cold Concurrent 8c) │ Cold:     2.45 ms │ Warm:     2.499 ms │ p95:     3.773 ms │   3,110 RPS ║
║ mixed (Cold Sequential)      │ Cold:     1.59 ms │ Warm:     1.028 ms │ p95:     1.679 ms │     971 RPS ║
║ mixed (Cold Concurrent 8c)   │ Cold:     0.40 ms │ Warm:     3.160 ms │ p95:     4.580 ms │   2,462 RPS ║
║ findById (Warm Sequential)   │ Cold:     0.65 ms │ Warm:     0.184 ms │ p95:     0.278 ms │   5,395 RPS ║
║ findById (Warm Concurrent 8c) │ Cold:     0.24 ms │ Warm:     0.931 ms │ p95:     1.324 ms │   8,498 RPS ║
║ findByIdRandom (Warm Sequential) │ Cold:     1.17 ms │ Warm:     0.285 ms │ p95:     0.451 ms │   3,494 RPS ║
║ findByIdRandom (Warm Concurrent 8c) │ Cold:     0.20 ms │ Warm:     0.999 ms │ p95:     1.575 ms │   7,946 RPS ║
║ listFilterSort (Warm Sequential) │ Cold:     0.91 ms │ Warm:     0.316 ms │ p95:     0.418 ms │   3,148 RPS ║
║ listFilterSort (Warm Concurrent 8c) │ Cold:     0.33 ms │ Warm:     1.006 ms │ p95:     1.304 ms │   7,744 RPS ║
║ listLarge (Warm Sequential)  │ Cold:     0.92 ms │ Warm:     0.454 ms │ p95:     0.767 ms │   2,191 RPS ║
║ listLarge (Warm Concurrent 8c) │ Cold:     0.39 ms │ Warm:     1.241 ms │ p95:     1.797 ms │   6,304 RPS ║
║ listPlain (Warm Sequential)  │ Cold:     0.94 ms │ Warm:     0.201 ms │ p95:     0.321 ms │   4,959 RPS ║
║ listPlain (Warm Concurrent 8c) │ Cold:     0.26 ms │ Warm:     0.775 ms │ p95:     1.005 ms │  10,122 RPS ║
║ findMissing (Warm Sequential) │ Cold:     0.70 ms │ Warm:     0.244 ms │ p95:     0.374 ms │   4,070 RPS ║
║ findMissing (Warm Concurrent 8c) │ Cold:     0.25 ms │ Warm:     0.666 ms │ p95:     1.915 ms │  11,830 RPS ║
║ create (Warm Sequential)     │ Cold:     2.50 ms │ Warm:     1.292 ms │ p95:     2.024 ms │     773 RPS ║
║ create (Warm Concurrent 8c)  │ Cold:     3.96 ms │ Warm:     5.223 ms │ p95:    10.072 ms │   1,522 RPS ║
║ update (Warm Sequential)     │ Cold:     2.77 ms │ Warm:     1.435 ms │ p95:     2.205 ms │     696 RPS ║
║ update (Warm Concurrent 8c)  │ Cold:     4.37 ms │ Warm:     5.388 ms │ p95:     7.942 ms │   1,469 RPS ║
║ graphql (Warm Sequential)    │ Cold:     2.08 ms │ Warm:     0.991 ms │ p95:     1.479 ms │   1,007 RPS ║
║ graphql (Warm Concurrent 8c) │ Cold:     1.01 ms │ Warm:     1.872 ms │ p95:     2.423 ms │   4,196 RPS ║
║ mixed (Warm Sequential)      │ Cold:     0.90 ms │ Warm:     0.980 ms │ p95:     1.715 ms │   1,019 RPS ║
║ mixed (Warm Concurrent 8c)   │ Cold:     0.57 ms │ Warm:     3.359 ms │ p95:     5.780 ms │   2,344 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                               MIDDLEWARE FLAMEGRAPH PROFILER (MARIADB)                                ║
║                         File: tests/benchmarks/middleware-flamegraph.test.ts                          ║
║                                       Ran: 2026-10-06 10:53:52                                        ║
║Measures isolated microsecond cost and incremental deltas of each middleware stage from edge to database.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Stage 0: Raw Socket Baseline (Static Asset) │ Cold:     3.41 ms │ Warm:     0.839 ms │ p95:     1.781 ms │   3,897 RPS ║
║ Stage 1: System State + Turbo Pipeline │ Cold:     1.60 ms │ Warm:     0.628 ms │ p95:     1.030 ms │   5,962 RPS ║
║ Stage 2: WAF Security Inspection │ Cold:     1.17 ms │ Warm:     0.634 ms │ p95:     0.826 ms │   6,094 RPS ║
║ Stage 3: Token Auth Gating   │ Cold:     3.35 ms │ Warm:     1.491 ms │ p95:     1.876 ms │   2,620 RPS ║
║ Stage 4: Collection Schema Resolution │ Cold:     5.63 ms │ Warm:     0.350 ms │ p95:     0.498 ms │  10,908 RPS ║
║ Stage 5: Full REST Single Document │ Cold:     2.34 ms │ Warm:     0.359 ms │ p95:     1.116 ms │   8,915 RPS ║
║ Stage 6: GraphQL Single Query (JIT) │ Cold:     3.07 ms │ Warm:     1.355 ms │ p95:     1.673 ms │   2,935 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

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

> ⏳ **EVENT LOOP LAG & SATURATION**: Pending execution. > 🎯 Measures event loop delay and microtask drain during continuous write bursts.

API · 9 tests

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

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — TEMPORAL INTEGRITY AUDIT ║ ║ File: tests/benchmarks/temporal-integrity.test.ts ║ ║ Ran: 2026-10-06 10:48:49 ║ ║Validates strict backend UTC normalization (ISO 8601 with trailing 'Z') across global timezone offsets, fractional timezones, and midnight transitions.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Temporal Ingestion & Normalization │ Cold: 4.77 ms │ Warm: 3.683 ms │ p95: 6.963 ms │ 950 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

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

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — RELATIONAL RESOLVER AUDIT ║ ║ File: tests/benchmarks/relational-performance.test.ts ║ ║ Ran: 2026-08-29 21:36:30 ║ ║Measures GraphQL resolver performance for shallow listings, deep relational joins, and nested author population across cold/hot execution paths.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Shallow Query (Collections) │ Cold: 3.00 ms │ Warm: 2.916 ms │ p95: 4.389 ms │ 1,949 RPS ║ ║ Deep Join (Cold DB) │ Cold: 2.68 ms │ Warm: 2.387 ms │ p95: 3.222 ms │ 1,595 RPS ║ ║ Deep Join (Warm Cached) │ Cold: 1.87 ms │ Warm: 1.872 ms │ p95: 2.880 ms │ 1,996 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

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

> [!NOTE] > **Specific to this test**: Avg degraded but p95 stable — possible cold-start effect, GC pause, or warmup variance. Throughput dropped 46% — check connection pool saturation or lock contention.

⏳ Auth & RBAC Performance: Pending execution. 🎯 Measures JWT verification, session retrieval, and permission matrix resolution overhead.

🏷️ REST API Performance · ⚪ 0.728ms · ↗️ — · 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 27% — check connection pool saturation or lock contention. **Severe degradation** (+34%) — review recent commits immediately.

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                 SVELTYCMS — ENTERPRISE REST API AUDIT                                 ║
║                          File: tests/benchmarks/rest-api-performance.test.ts                          ║
║                                       Ran: 2026-10-06 10:46:37                                        ║
║Measures latency, throughput, and correctness of core REST endpoints: health check, schema, single read, list, and search.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ System Health Check          │ Cold:     1.04 ms │ Warm:     0.728 ms │ p95:     1.139 ms │   5,335 RPS ║
║ Collection Schema Metadata   │ Cold:     6.70 ms │ Warm:     0.518 ms │ p95:     0.807 ms │   7,291 RPS ║
║ Single Document Read         │ Cold:     2.81 ms │ Warm:     0.414 ms │ p95:     0.620 ms │   9,075 RPS ║
║ Collection Find (List Limit 20) │ Cold:     5.60 ms │ Warm:     0.569 ms │ p95:     0.839 ms │   6,799 RPS ║
║ Collection Search Query      │ Cold:     1.99 ms │ Warm:     0.626 ms │ p95:     0.944 ms │   6,122 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

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

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — GRAPHQL CACHE HIT AUDIT                                  ║
║                           File: tests/benchmarks/graphql-cache-hit.test.ts                            ║
║                                       Ran: 2026-10-06 10:53:14                                        ║
║        Validates sub-millisecond L1 response cache hits, cache key isolation, and hit headers.        ║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Q1: Health (Cold Miss)         │        3.140 ms │ p95:        3.140 ms │ RPS:        318 ║
║ Q1: Health (L1 Hit)            │        1.047 ms │ p95:        1.260 ms │ RPS:        955 ║
║ Q2: Collections (Cold Miss)    │        2.670 ms │ p95:        2.670 ms │ RPS:        375 ║
║ Q2: Collections (L1 Hit)       │        1.073 ms │ p95:        1.562 ms │ RPS:        932 ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Enterprise SEO Suite Audit · ⚪ 1.568ms · ↘️ — · source

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                   SVELTYCMS — ENTERPRISE SEO AUDIT                                    ║
║                            File: tests/benchmarks/seo-performance.test.ts                             ║
║                                       Ran: 2026-10-06 10:47:56                                        ║
║Measures redirect lookup latency, dynamic sitemap.xml generation, robots.txt serving, and 404 logging performance.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Redirect Lookup (301)        │ Cold:     2.04 ms │ Warm:     1.653 ms │ p95:     2.827 ms │   4,795 RPS ║
║ Dynamic Sitemap XML          │ Cold:  1885.73 ms │ Warm:     1.465 ms │ p95:     1.763 ms │   5,410 RPS ║
║ Robots.txt Generation        │ Cold:     2.56 ms │ Warm:     1.568 ms │ p95:     2.507 ms │   5,063 RPS ║
║ Missing Path (404 Log)       │ Cold:   157.58 ms │ Warm:   224.283 ms │ p95:   277.537 ms │      36 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

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

> ⏳ **REAL-TIME BROADCAST AUDIT**: Pending execution. > 🎯 Benchmarks network-layer broadcast latency (SSE vs WebSocket).

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

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

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

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

⏳ GraphQL Response Cache Hit: Pending execution. 🎯 L1 response cache: cold-query vs cache-hit latency verification.

Scale · 18 tests

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

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                             SVELTYCMS — NEGATIVE CACHE PERFORMANCE AUDIT                              ║
║                             File: tests/benchmarks/negative-cache.test.ts                             ║
║                                       Ran: 2026-10-06 10:47:12                                        ║
║Measures Bloom-filter style missing-key cache speedup for repeated misses against direct database miss baselines.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Direct DB Miss Baseline      │ Cold:     5.13 ms │ Warm:     0.865 ms │ p95:     1.240 ms │   1,098 RPS ║
║ Cold Miss (Bypass Cache)     │ Cold:     8.52 ms │ Warm:     0.874 ms │ p95:     1.181 ms │   1,099 RPS ║
║ Hot Miss (Negative Cache)    │ Cold:     0.29 ms │ Warm:     0.001 ms │ p95:     0.002 ms │ 766,056 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Revision & History Growth · ⚪ 0.349ms · ↘️ — · 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 10:49:16                                        ║
║Measures latest read degradation, history retrieval speed, and storage footprint under heavy revision growth (100 revisions).║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Clean Document Read (Baseline) │ Cold:     4.42 ms │ Warm:     0.407 ms │ p95:     0.579 ms │   9,563 RPS ║
║ Latest Read (100 Revisions)  │ Cold:     2.50 ms │ Warm:     0.349 ms │ p95:     0.571 ms │   9,990 RPS ║
║ History List Retrieval       │ Cold:     9.14 ms │ Warm:     1.959 ms │ p95:     2.980 ms │     994 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 · ⚪ 1.069ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — MULTI-TENANCY PERFORMANCE AUDIT ║ ║ File: tests/benchmarks/multi-tenant-performance.test.ts ║ ║ Ran: 2026-10-06 10:47:18 ║ ║Measures the overhead of tenant isolation, context switching, and data partitioning across many tenants.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Single Tenant Baseline │ Cold: 5.41 ms │ Warm: 1.484 ms │ p95: 3.430 ms │ 4,714 RPS ║ ║ Multi-Tenant Context Switching │ Cold: 0.83 ms │ Warm: 1.069 ms │ p95: 1.591 ms │ 7,091 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

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

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — MIXED WORKLOAD AUDIT ║ ║ File: tests/benchmarks/mixed-workload.test.ts ║ ║ Ran: 2026-10-06 10:47:59 ║ ║Simulates real-world traffic with a weighted mix of reads, searches, GraphQL queries, and metadata requests with per-operation telemetry.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Mixed Workload │ Cold: 7.39 ms │ Warm: 0.765 ms │ p95: 2.397 ms │ 7,687 RPS ║ ║ Mix: REST Read │ 0.887 ms │ p95: 1.302 ms │ RPS: 2,006 ║ ║ Mix: REST Search │ 0.885 ms │ p95: 1.392 ms │ RPS: 679 ║ ║ Mix: GraphQL │ 2.425 ms │ p95: 4.210 ms │ RPS: 543 ║ ║ Mix: Metadata │ 0.968 ms │ p95: 2.322 ms │ RPS: 168 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ GraphQL Load Stress · ⚪ 15.753ms · ↗️ — · 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** (+165%) — review recent commits immediately.

⏳ GraphQL Load Stress: Pending execution. 🎯 High-concurrency GraphQL query stress test for resolver efficiency.

🏷️ Bulk Migration & Scale · ⚪ 0.501ms · ↘️ — · source

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

╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗
║                                  SVELTYCMS — MIGRATION & SCALE AUDIT                                  ║
║                            File: tests/benchmarks/migration-scale.test.ts                             ║
║                                       Ran: 2026-10-06 10:51:23                                        ║
║Measures bulk ingestion throughput for 10,000 entries, random point-lookups, and indexed range scans across large datasets.║
╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣
║ Bulk Migration (10k docs)    │ Cold:    37.33 ms │ Warm:    13.101 ms │ p95:    38.513 ms │  28,965 RPS ║
║ Random Point Lookup          │ Cold:     6.26 ms │ Warm:     1.983 ms │ p95:     3.469 ms │   2,869 RPS ║
║ Range Scan & Pagination      │ Cold:   152.25 ms │ Warm:     0.501 ms │ p95:     1.062 ms │  10,155 RPS ║
╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝

🏷️ Million-Row Index Pressure · ⚪ 0.704ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — INDEX PRESSURE AUDIT ║ ║ File: tests/benchmarks/index-pressure.test.ts ║ ║ Ran: 2026-10-06 10:49:06 ║ ║ Measures read performance with sorting and filtering on a large entry collection. ║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Sorted List (25k rows) │ Cold: 23.42 ms │ Warm: 0.704 ms │ p95: 0.980 ms │ 5,643 RPS ║ ║ Filtered Query (25k rows) │ Cold: 6.72 ms │ Warm: 0.581 ms │ p95: 0.874 ms │ 6,834 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

🏷️ Content Scale Stress · ⚪ 0.135ms · ➡️ — · source

> ⏳ **Content Scale Stress**: Pending execution. > 🎯 Measures content scan performance on 1,000+ collections under .compiledCollections/test/stress (isolated).

🏷️ Media Upload Stress & Throughput · ⚪ 9.393ms · ➡️ — · source

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — MEDIA UPLOAD STRESS AUDIT ║ ║ File: tests/benchmarks/media-upload-stress.test.ts ║ ║ Ran: 2026-10-06 10:51:11 ║ ║Measures throughput for large file uploads, concurrent transfers, and streaming efficiency with valid media fixtures.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Single Upload (0.01MB) │ Cold: 27.90 ms │ Warm: 8.688 ms │ p95: 9.250 ms │ 115 RPS ║ ║ Small Upload (0MB @ 4c) │ Cold: 8.09 ms │ Warm: 9.393 ms │ p95: 10.556 ms │ 424 RPS ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

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

> ⏳ **Full Client Journey Simulation**: Pending execution. > 🎯 E2E journey: Login -> List -> View -> Edit -> Save -> Realtime. Measures cumulative latency.

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

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

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

``` ╔═══════════════════════════════════════════════════════════════════════════════════════════════════════╗ ║ SVELTYCMS — DIRECT ADAPTER THROUGHPUT (MARIADB) ║ ║ File: tests/benchmarks/local-api-throughput.test.ts ║ ║ Ran: 2026-10-06 10:49:18 ║ ║Measures direct adapter write throughput, read throughput, and percentile latencies with zero HTTP overhead.║ ╠═══════════════════════════════════════════════════════════════════════════════════════════════════════╣ ║ Writes (1000 atomic increments) │ 1.093 ms │ p95: 2.963 ms │ RPS: 6,794 ║ ║ Reads (1000 point lookups) │ 1.291 ms │ p95: 2.756 ms │ RPS: 9,765 ║ ╚═══════════════════════════════════════════════════════════════════════════════════════════════════════╝ ```

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

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

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

> ⏳ **Failure Propagation & Fast-Fail Audit**: Pending execution. > 🎯 Measures system overhead when downstream dependencies (DB/Redis) fail or timeout.

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

> ⏳ **Chaos & Infrastructure Resilience**: Pending execution. > 🎯 Simulates 500ms database brownouts and measures CMS availability and stability.

🏷️ Production Day Simulation · ⚪ 2.373ms · ➡️ — · 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

> ⏳ **Throttling & Backoff Stress**: Pending execution. > 🎯 Measures rate-limiting consistency under 10x design load.

🏷️ 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

> ⏳ **Database Failover & Reconnection**: Pending execution. > 🎯 Simulates DB disconnect mid-request — measures circuit breaker activation and reconnection timing.

🔬 Host environment

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