A small timeline's catalogue text sorts its moments instead of walking (#285)
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
oc_event_text walked the moment tree a statement per step, several on a fork (a live then a retired version at each level it reads through), so rebuilding a 5,000-moment fork's text after its source's saves took about 2 s. A timeline of at most 50,000 moments now sorts all its moments' IDs in one query (oc_moments_at for a fork's levels) and reads them by ID a page at a time, still stopping once the text is full; larger ones walk as before. JIT is off for the rebuild, whose compiling took longer than running it. Forks: 1.95 s to 0.25 s at 5,000 moments, 5.7 s to 0.6 s at 20,000, 7.6 s to 0.8 s at 50,000; plain timelines about twice as fast at 5,000; 200,000 unchanged. bench/fork-text.mjs measures it. The catalogue test checks both ways of reading against the reference. bench/fork-reads.mjs copies its timeline as a duplicate: since #262 an owner cannot fork their own timeline. Closes #285 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/ec47535e590e366b39bc231249a38641def75ab6
Related
Open A small timeline's catalogue text sorts its moments instead of walking (#285) in the timeline