v149 · Storage · IndexedDB
Concurrent Reads Test
Open N read-only transactions simultaneously and verify that all return correct data. A key claim of the SQLite migration: concurrent reads should see a consistent snapshot and never block each other.
Concurrent transactions
8
Records per store
1000
Reads per transaction
50
Press run to start the test…
what this tests
The SQLite backend moves IndexedDB onto a single SQLite file per origin. Concurrent read-only transactions must each see a consistent snapshot — SQLite's reader-writer locks ensure readers don't block each other. This test opens N transactions at the same instant and verifies every read returns the value that was written during setup, with no torn reads.
see also
- Error Recovery — abort correctness and durability
- Bulk Write Stress Test — write throughput
- Transaction Durability — atomicity checks
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗