circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#199 och-convert can't write large timelines within its CPU limit

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#199
  • issue
  • state:closed

Found while fixing #193. `och-convert write` (server `.och` exports) runs under a 20 s CPU limit (`RLIMIT_CPU`, `native-store/src/bin/och-convert.rs`). Filling the overview index (`points`, the `rational_index` virtual table) costs about 0.35 ms per distinct moment time. That holds for one bulk insert and for one insert per time alike. So a conversion runs out of CPU at roughly 45–50k moments, well under the 200,000 the format allows. Measured on a release build (moments only): | Moments | Overview index | Result | | --- | --- | --- | | 10,000 | ~3.5 s | ok | | 30,000 | ~12 s | ok | | 200,000 | — | killed at the CPU limit | #193 fixed the earlier failure: the instruction budget was shared by the whole conversion and ran out near 9,000 moments. What's left is the index's own insert cost, or the limit chosen for it. Options: - a bulk-load path in sqlite-rational for sorted input, building the tree bottom-up; - a CPU limit that scales with the input's size. My (Athan) recommendation: Make the conversion a streaming process so the event loop isn't occupied for a long time. Additionally, make a size limit for how saves / exports should be allowed for all users except admin or privileged accounts. Its a threat vector that doesn't seem to currently scale well, even if there's a fleet of openchronology servers load balanced - unless the process is cacheable in redis or something. https://github.com/openchronology/timeline-app/issues/199

Related

Open #199 och-convert can't write large timelines within its CPU limit in the timeline

#199 och-convert can't write large timelines within its…