demo · v144
Transaction Stress
The new SQLite backend changes how Chrome stores IDB data, not the API. The wins show up under stress: concurrent transactions, large reads, long-running writes. Run the stress test and watch p50/p99 latency, throughput, and failure rate. Open the page in regular and incognito tabs to compare.
IndexedDB: checking…
write latency
- p50 / p99
- —
- throughput
- —
- failures
- —
read latency
- p50 / p99
- —
- throughput
- —
- failures
- —
what changed
// no JS change — same API, new storage engine
const db = await openDB("notes");
await db.put("k", value);
await db.get("k");
// Chrome 144: in incognito + memory-constrained contexts, IDB is now backed
// by SQLite in-memory. Tighter concurrency model, ACID semantics, better
// reliability when the OS evicts pages.