Keep saves fast right after a large timeline is written
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
After a large whole-timeline write (fork, create, import), the index tables' statistics are refreshed after commit and before the request returns, and the save path's lookups by key (tree paths, incremental saves, catalogue text) stay one index lookup per key whatever the statistics say. A 10-moment save right after forking a 200,000-moment timeline drops from 5.3 s to 0.16 s. Fixes #139. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/c2f84a8166e0bfa7c70654f27bd1261e86ca894e
Related
Open Keep saves fast right after a large timeline is written in the timeline