demo · v149
Bulk Write Stress Test
Inserts N objects of size S bytes each into IndexedDB, then reads them back, scans with a cursor, and labels the run with the best available Chrome SQLite-backend inference.
backend probe
Active backend label
IndexedDB does not expose the storage engine to page JavaScript, so this page separates the direct signal from a rollout-based inference.
- direct JS signal
- No standard API exposes LevelDB vs SQLite.
- browser milestone
- Checking user agent...
- store state
- Checking database list...
- storage estimate
- Checking quota metadata...
run history
The last eight runs are saved locally so cold, warm, normal-window, and incognito runs can be compared without leaving the page.
| time | backend label | objects | size | write | read | scan | checks |
|---|
how to read the label
ChromeStatus describes this as a staged, no-web-API change. Incognito/in-memory contexts were tracked in step 1, this step applies the SQLite-backed path to new persistent IndexedDB stores, and existing LevelDB stores wait for a later migration step. If the page opens an old store, the safest label is "unobservable"; wipe the database to create a new store under the current Chrome rollout or flag state.
see also
- IndexedDB: SQLite backend — feature index
- Transaction Durability — rollback and durability checks
- ChromeStatus entry — step 2
- IndexedDB spec
implementation reference
Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗