- Introduced export schema for JSON data structure. - Created renderer contract detailing canvas/SVG rendering requirements. - Defined IndexedDB storage schema and migration strategies. - Documented data model including entities and relationships. - Developed implementation plan outlining execution flow and project structure. - Provided quickstart guide for development environment setup. - Compiled research documentation on performance, accessibility, and theming. - Established feature specification with user scenarios and functional requirements.
32 lines
1.0 KiB
Markdown
32 lines
1.0 KiB
Markdown
# Research: IndexedDB Imports & Migrations
|
|
|
|
## Hypothesis
|
|
Chunked transactions and store-per-entity design yield responsive imports and safe migrations for 3-year datasets.
|
|
|
|
## Questions
|
|
- Import throughput (items/sec) for days vs entries
|
|
- Optimal chunk size per transaction
|
|
- Quota usage for 3-year dataset
|
|
- Migration time and error handling patterns
|
|
|
|
## Method
|
|
- Use `/packages/storage/poc/import-benchmark.html`
|
|
- Measure timings, DB size; simulate version bump
|
|
|
|
## Test Matrix (fill during runs)
|
|
| Chunk | Days(ms) | Entries(ms) | Notes |
|
|
|-------|----------|-------------|-------|
|
|
| 100 | | | |
|
|
| 250 | | | |
|
|
| 500 | | | |
|
|
| 1000 | | | |
|
|
| 2000 | | | |
|
|
| 5000 | | | |
|
|
|
|
## Acceptance
|
|
- Import < 5s for 3-year synthetic dataset on mid device
|
|
- Migrations complete without UI lockup and preserve data
|
|
|
|
## Deliverables
|
|
- Import strategy, migration template, data integrity checklist
|