One Big-ass Org File or multiple tiny ones?
summary
Compares one giant Org file (example: 126,000 lines causing ~20 seconds agenda build) versus many small files used by org-roam, and explains why the bottleneck is the org-element parser needing to parse everything in a single-threaded Emacs. Reports a personal setup: main GTD file at 38,000 lines, agenda optimized to under 2 seconds by rewriting parsing code, recommends archiving done items and splitting note-taking from task management to reduce parse and rendering costs.
AI-written summary · about
chapters (7)
- 0:00Introduction and title
- 0:43The Org Mode debate
- 3:54Org-element and parsing
- 7:20Optimizing agenda build time
- 8:44Answering the big question
- 13:02Archiving and performance
- 14:51File sizes and resources
related talks
46mThe Underrated (But Amazing) Emacs org-mode
47mOrg-Mode for Science, Reproducible Research, and Organization
39mScaling Xtext
39mArch. App: Prioritizing Technical Debt as if Time and Money Matters
28mAchieving Economies of Scale in Cloud IDEs
07mSwiping Left on Monolithic Targets
13mJest - RAM Eater
14mGang up on difficult problems with Mob Programming