I went and tested how Deepdwn handles progressively larger numbers of files by adding in duplicates of that folder, stopping at 25MB.
if someone writes prolifically in it they will simultaneously write themselves out of being able to use it
First, in general, I think this form of artificial benchmarking isn’t particularly useful, and this example strikes me as somewhat unrealistic. Math follows.
While 25mb doesn’t sound like a whole lot these days, keep in mind that markdown is a plain text format, so that 25MB is doing a whole lot of work.
If 30kb represents about 10,000 words (depends on things like file encoding/content etc.), and took roughly a week, you would have needed to create something like 800 duplicates of that folder, totalling more than 10,000 individual files that Deepdwn needs to read, manage and monitor for changes.
If you were to write at your current output of 10,000 words/week (and required no editing), you’d reach one copy of War and Peace (600,000 words, 1200+ pages, 3.1MB) in about 14 months.
To reach 25MB (~5,000,000 words, 9,600 pages), then, would require you to maintain that same continuous output, every week, until 2030.
I’m not sure that means that Deepdwn “doesn’t scale”, so much as that there are potential use cases that Deepdwn isn’t designed for, and that might include: tens of thousands of markdown files that Deepdwn needs to be aware of and parse, with millions of words. I don’t think that excludes prolific writers, who are certainly among Deepdwn’s target users.
That all said, there are improvements that can be made to the way Deepdwn handles extremely large collections of files and/or large files. Those will likely happen when the search functionality is rebuilt, but I don’t have an ETA for that.
I’m going to be following Deepdwn’s development and trying new versions as they come out
Great! If it isn’t a good fit for you now, I hope that it will be some day in the future (and hopefully before 2030).