I’m loving org-roam, and, like many here, care about the longevity of my note system. With my habits (e.g. making nodes for most humans I interact with), I could easily end up with 10,000+ nodes in a few years. If that’s unlikely to be workable with org-roam, it would be good to know!
After searching through the code / tests / GH issues / Slack, I found very little info on the scalability of org-roam’s current implementation. I thought it would be good to aggregate info here, and make GH issues (e.g. scaling tests) as-needed.
Some things I’ve noticed so far:
- at ~500 nodes, most core operations are snappy for me
- running org-roam-insert on a new entity takes ~3-5 seconds until the link is inserted.
- I imported ~400 more nodes from Roam yesterday, and had no noticeable slowdown.
- Tangentially related: org-agenda can’t handle large numbers files, so I’ve been using capture templates with backlinks to workaround this. This is unfortunate, since interspersing TODOs directly in the nodes is a great Roam feature IMO.
Is anybody operating at near the 10,000 node scale?