Skip to content

Performance notes ​

Comparable Chromium numbers for docs and README — not the soft-ceiling regression suites (test:perf / bench:e2e).

What we measure ​

Sequential put/get + index query through createDatabase (mode: 'shared') vs the same shapes on Dexie (main-thread IndexedDB). Plus a cross-tab subscribe fan-out number for the SharedWorker product story (Dexie has no equivalent path in this bench).

Caveats ​

  • Same machine / same run only — absolute ops/s move with CPU load; prefer ratios from one run.
  • Dexie is a fair IndexedDB baseline for single-tab CRUD. It does not include SharedWorker multi-tab live sync.
  • worker-sync-db pays RPC + SharedWorker overhead on every op; that is intentional and what you buy multi-tab consistency with.

Latest marketing snippet ​

Committed outputs from npm run bench:marketing live in the repo under docs/benchmarks/.

Workloadworker-sync-dbDexie (baseline)Notes
Put throughput (200 sequential)2.69k ops/s4.45k ops/sSame docs; WSD pays SharedWorker RPC
Get throughput (200 sequential)8.44k ops/s14.18k ops/sKey lookup
Put latency p50 / p950.20 / 0.50 ms0.20 / 0.40 msSingle-op samples (n=50)
Get latency p50 / p950.10 / 0.20 ms0.10 / 0.20 msSingle-op samples (n=50)
Cross-tab fan-out (40 puts → 2nd tab)690 events/s (58.0 ms wall)—Dexie has no SharedWorker multi-tab path

Last run: 2026-10-09 · Chromium (Playwright Desktop Chrome)

Interactive benches ​

The demo build also ships optional bench pages (same Pages deploy):

Regenerate committed snippets after meaningful client/worker changes — see docs/benchmarks/README.md.

MIT License · offline-first IndexedDB with SharedWorker sync