4 ms·
I use tiddlywiki (with the nodejs setup) regularly. It's great until your wiki grows too large, at which point you need to wait ~10s for it to load even with m
by RyEgswuCsn 4y ago
I use tiddlywiki (with the nodejs setup) regularly. It's great until your wiki grows too large, at which point you need to wait ~10s for it to load even with modern hardware.
- rpdillon 4y agoI'd be very curious to hear about the sizes and use cases where you're seeing this. My understanding was that single file wikis could scale to a hundred megabytes and beyond, and I thought the nodejs version was more scalable than that due to lazy loading tiddlers. My wikis tend to be less than 20mb since I mostly use plain text for everything.
- RyEgswuCsn 4y agoI do make use of the `backlinks` query extensively, and I use saqimtiaz's wonderful `streams` [1] plugin to recreate a Roam-like experience. This setup leads to a large amount of small-sized tiddlers (2.5k and counting), which might add to the overhead. Not to mention downloading and parsing 20mb-worth of html+js each time you open up the wiki can be quite slow. As for lazy loading --- when enabled, it breaks the indexing (e.g. finding backlinks) and searching because these are done by the js inside the browser too. I only lazy-load images and binaries because they are not indexable anyway. [1]: https://github.com/saqimtiaz/streams https://github.com/saqimtiaz/streams