Erwan Excellent bit of research you did on TiddyWiki Performance <http://erwanm.github.io/tw-community-search/#TagsOptimizations> -- I bookmarked it to study later.
FYI, I been playing with TiddlyWiki as an e-pub format. Once the file gets beyond a smaller size and complexity performance issues begin to matter. I'm still not sure if its really viable for enhanced e-pubs when they get larger. Structurally its ideal, allowing easy annotation, bookmarking etc. But possibly not in terms of performance. Best wishes Josiah On Saturday, 11 March 2017 20:34:24 UTC+1, Erwan wrote: > > Hi, > > In case anyone finds this thread later, it might be worth mentioning that > extensively using tags puts a strain on large wikis. Using fields instead > (everywhere where possible/relevant) can significantly improve the overall > performance. see a case study at: > http://erwanm.github.io/tw-community-search/#TagsOptimizations > <http://www.google.com/url?q=http%3A%2F%2Ferwanm.github.io%2Ftw-community-search%2F%23TagsOptimizations&sa=D&sntz=1&usg=AFQjCNE61bVpXZ61XprIgZkcpEQw4kFV4Q> > > Erwan > > On 26/01/17 14:00, Nick Gibbins wrote: > > Hi, > > I'm currently having difficulties with a rather large TW that I'm > constructing, containing roughly 25,000 tiddlers (it's a specialised > encyclopedia). Total file size is less than 20Mb; the majority of the > tiddlers are small, but contain structured data in custom fields. I'm using > TW version 5.1.13 and Firefox 50.1.0 under OS X 10.12.2. The machine I'm > using has an SSD. > > If I treat my TW as a single file, I get save times in excess of 120s > (autosave is therefore not an option). > > If I use node.js as a backend, opening or closing each tiddler typically > takes around 50s (the server console suggests that much of this time is > spent on the save task for $:/StoryList). During this time, the browser is > unresponsive. > > I also fairly often see the following error, typically when opening the TW > when the server has already been running for longer than a few minutes. > > RangeError: Maximum call stack size exceeded > at Logger.log ($:/core/modules/utils/logger.js:29:108) > at Syncer.dispatchTask ($:/core/modules/syncer.js:495:15) > at Syncer.processTaskQueue ($:/core/modules/syncer.js:417:9) > at $:/core/modules/syncer.js:425:27 > at $:/core/modules/syncer.js:505:4 > at FileSystemAdaptor.loadTiddler > ($:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:201:2) > at Syncer.dispatchTask ($:/core/modules/syncer.js:496:20) > at Syncer.processTaskQueue ($:/core/modules/syncer.js:417:9) > at $:/core/modules/syncer.js:425:27 > at $:/core/modules/syncer.js:505:4 > > Any and all suggestions would be welcome at this point, including "you > fool, you're using TW for things that it wasn't designed for". > > Thanks, Nick > > > > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/ea3947a7-c49f-4102-9b2b-a24e05810f02%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/ea3947a7-c49f-4102-9b2b-a24e05810f02%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/40a0cd6d-39cc-4f55-90d9-70e5dcb2c466%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
