Thanks Jeremy. I feel like an utter twat :-) But I don't mind as I think your answers are really useful to see.
Jeremy Ruston wrote: > > Just to clarify some of the points made by Josiah: > > As far as I understand it the problem is not the DOM per se, which > TiddlyWiki does not handle in the standard way, its the REFRESH mechanism. > Everything has to be rebuilt when a change is made. The problem with this > is that the more complex the TW gets the worse performance (generally) gets. > > > It’s not really correct to say that TiddlyWiki doesn’t handle the DOM in > the standard way. It’s more that it doesn’t use the DOM in the old > fashioned way. All modern React apps, for instance, work the same way that > TiddlyWiki works. > > And it’s not quite right to say that everything needs to be rebuilt when a > change is made. The refresh mechanism endeavours to make the minimal, > selective updates to the DOM to reflect changes to the store as they occur. > > But the conclusion isn’t far off: to be more precise, performance depends > on the complexity of the page — ie the results of rendering the > $:/PageTemplate tiddler. > > Its certainly worth comparing if a Node.js might work better. But its > likely there is a limit. > > > It is *not* worth comparing with performance under Node.js. As other > posters have pointed out, loading the wiki from a Node.js server doesn’t > affect the performance of what happens in the browser. > > If it works better it won't be because of "lazy loading" since, as PMario > says, in your usage as the issue centres on Tiddlers could be invoked in > lists/filters. "Lazy loading" relates to simply that the Title only is > permanently in memory--and the Tiddler content loads on click. It won't > speed up lists or filters. > > > Indeed, execution of filters is a substantial proportion of overall > rendering time. > > In brief, at the moment, TW does not scale well. > > > Again, I don’t think that’s hugely helpful as a blanket statement, For > example, I’m working with a 65MB TW5 at the moment, and it works fine on my > 2013 laptop. > > Perhaps better to say that as a TiddlyWiki gets more complex one has to > pay more attention to performance. > > Since I am a bit of an amateur (I'm not a programmer) others may say > otherwise... but I wrote this to hopefully elicit clearer answers. > > > Indeed, your comments are helpful, > > Best wishes > > Jeremy. > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. 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/f0b9472e-543d-4210-9470-423fc303f090%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
