.och conversions hold less memory, and their file limit is a setting (#202)
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
save() no longer copies the whole document (only one with legacy duration links is copied to convert them), and och-convert write keeps each moment's metadata as raw JSON until save_streamed writes that moment: 200,000 moments peak at 92 MB instead of 404 MB. TIMELINE_FILE_BYTES (1 MiB to 1 GiB, 64 MiB by default) sets the largest .och file the server exchanges: uploads, exports, och-convert's input and output (OCH_FILE_BYTES), and its memory limit (512 MiB, or eight times the file limit). The session tells the editor the limit. A conversion stopped by a limit now says which: time, file size or memory. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/8d46cc20258db308bd1addd32a0dedf38c07bd5b
Related
Open .och conversions hold less memory, and their file limit is a setting (#202) in the timeline