Hi Mat The refresh mechanism is sufficiently complex that there is great scope to optimise and improve it. We don’t currently use the technique you describe of suppressing refreshes for a portion of the tree, but it’s something that would be fairly trivial to explore: it’s just a matter of introducing a parent widget that selectively passes on refreshes to its children. The obvious problem with it is that it would lead to different parts of the tree being out of step with one another.
The dirtiest optimisation technique we currently use is to suppress updates to draft tiddlers until there is a pause in typing. Best wishes Jeremy > On 8 Jun 2019, at 11:56, Mat <[email protected]> wrote: > > Admittedly, this question is too advanced for me but I'd still like to hear > an answer even if only "Nope, impossible to change" or "Possible" > > I suspect one of the biggest culprits for slowness is nested lists with > complex filters. I.e pretty much the very point with TW. For an example, I > think we even had to snip the native Recent list to prevent this but lags can > easily get a lot more severe. > > Naturally there is a lag when such a tiddler is opened/activated but the > freeze also happens when such a tiddler is already open and you change > someting something else on the page like create a new tiddler, even an empty > one. Is this perhaps because such filters typically evaluate all tiddlers to > see if they fulfill the filter criteria, including that new empty one? It's > as if one has to redo the whole house every time a kitchen chair is moved. > > So I ask; must necessarily the whole page be re-calculated even when one is > not necessarily dealing with the complex tiddler in question? Specifically, > could such complex tiddler(s) be isolated from the re-calculation of the > page? Maybe a tiddler-local flag ("do not refresh this tiddler")? > > Maybe the node version does things differently? > > Thank you > > <:-) > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <https://groups.google.com/group/tiddlywikidev>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/026d9d76-a80e-44e0-9870-4671bd857fc4%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywikidev/026d9d76-a80e-44e0-9870-4671bd857fc4%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/148BCFC5-727A-4C2A-80FB-B198EADC20A5%40gmail.com. For more options, visit https://groups.google.com/d/optout.
