Large .duckdb files contain dense GPS and channel data that stress browser memory and GPU.
Symptoms
- Slow initial load
- Replay stutter
- 3D view frame drops
- Browser tab high memory usage
Recommendations
| Tip | Why |
|---|---|
Use 2D map (M) | Much lighter than 3D WebGL |
| Avoid multiple overlays | Each modal adds render cost |
| Close other heavy tabs | Large telemetry files use significant browser memory |
| Quit other heavy apps | Games and overlays compete for CPU/GPU with 3D replay |
| Use a desktop browser | Most complete layout; mobile is supported but simplified — see Viewing & performance |
| Shorter sessions | Long races produce 50MB+ files |
Threshold
Files over 50 MB commonly cause 3D stutter. Switch to 2D map first.
Pro file size
Pro removes the 20 MB upload cap — very large files upload but may load slowly.