blob: 22a831803b46e3174b842ef583a06299e8433ff4 (
plain) (
tree)
|
|
[[!meta title="One Big-ass Org File or multiple tiny ones? Finally, the End of the debate!"]]
[[!meta copyright="Copyright © 2020 Leo Vivier"]]
Back to the [[schedule]]
Previous: <a href="/2020/schedule/11">the org-gtd package: opinions about Getting Things Done</a>
Next: <a href="/2020/schedule/13">Experience Report: Steps to "Emacs Hyper Notebooks"</a>
# One Big-ass Org File or multiple tiny ones? Finally, the End of the debate!
Saturday, Nov 28 2020, 1:52 PM - 2:02 PM EST / 10:52 AM - 11:02 AM PST / 6:52 PM - 7:02 PM UTC / 7:52 PM - 8:02 PM CET / 2:52 AM - 3:02 AM +08
Leo Vivier
Many discussions have been had over the years on the debate between
using few big files versus many small files. However, more often than
not, those discussions devolve in a collection of anecdotes with
barely any science to them.
Once and for all (or, at least until org-element.el get overhauled), I
would like to settle the debate by explaining why the way we parse
Org-mode files becomes slower as our files grow in size or numbers,
and how that affects their browsing and the building of custom-agenda
views.
I feel qualified to talk about this topic for two reasons:
- I went through the trouble of optimising my agenda-views by
implementing clever regex-based skips, so I know the ceiling that
can be reached with the current tech.
- My work on Org-roam has led me to consider the use of an external
parser for Org-mode files, and whilst we are only at the prototyping
stage, we know what is at stake.
I intend the talk to be fairly light-hearted and humorous, which is the
only way we can do true justice to the topic.
Back to the [[schedule]]
Previous: <a href="/2020/schedule/11">the org-gtd package: opinions about Getting Things Done</a>
Next: <a href="/2020/schedule/13">Experience Report: Steps to "Emacs Hyper Notebooks"</a>
All times are approximate, and we might shuffle talks around as needed.
Please check <https://emacsconf.org/2020> a few days before the start of the
conference for instructions on how to watch and participate. See you then!
<!-- automatically generated from submissions.org using conf/generate-schedule-files --->
|
