Thanks for the helpful response!
I’ve just been using Dynalist a short time but finding it very useful. So my question was more looking towards the long term rather than an immediate need.
My main Dynalist file is 115 kb at the moment, but I can see it easily growing to 10X that in less than a year by extrapolating the growth over the last couple months.
I tried the sample file, but perhaps I’m confused, as it seems to be separated into several documents each of fairly modest size. Does the performance of this group of documents demonstrate the performance of a single large document?
Clearly I’m confused and hopefully you can straighten me out.
[Edited a few minutes later]…I may have figured out the point. The document under Scholars > Propædia is 936 KB when I export it as an OPML, so that’s apparently the document you wanted me to see to demonstrate performance of a ~1MB file.
I see that it does respond with a bit of lag when all branches are open and the document has just been loaded. As I page down thru the document, it takes a moment for each new page to load. If I expand/collapse all nodes it takes about 5 seconds to respond to that command.
But if I collapse to the top level nodes and just open them one at a time, response is very snappy and there’s virtually no lag. Also, after the document has been loaded and used, it’s a bit more responsive than when first loaded. Finally, and most critically for me, searches are very responsive and quickly narrow down the text to a topic of interest.
Now that I see what you were trying to show me, the demo does answer my question very effectively. I can see directly how a 1 MB OPML file responds.
As I would never have cause to have all nodes open simultaneously, I can see from the demo the kind of response I would actually experience in a scenario that’s realistic for me.
Thank you so much for answering my question so well. My concerns on document size have been put in perspective and I doubt I’ll worry about it much again.