> > IN FACT the whole question of Performance in TW deserves a lot more > attention IMO.
The performance has improved a lot since the early versions of TiddlyWiki5. I remember some of the early advances between 5.0.4 (when popups took a second to open) and 5.0.14 (400 ms or so). Now they are nearly instantaneous! So work has been done, but filters is one that does still need it. One only has to open the list of shadow tiddlers to get a good benchmark. But that time has improved too. Maybe we could compile filters... On Mon, Jun 26, 2017 at 8:24 PM, Arlen Beiler <arlen...@gmail.com> wrote: > It was on an almost empty TiddlyWiki datafolder mounted in TiddlyServer > (which currently uses $:/core/save/all), so just a stock TiddlyWiki with > hardly anything in it. I didn't think about it that I was using an almost > empty TiddlyWiki or I would have mentioned it! :) > > Windows 7 64 Bit / Chrome current stable. > > On Mon, Jun 26, 2017 at 8:10 PM, 'Mark S.' via TiddlyWiki < > tiddlywiki@googlegroups.com> wrote: > >> Hi Arlen, >> >> What is your setup? Nodejs or stand-alone? Which browser, what OS, and >> what kind of machine. I'm thinking that if you can zip through these in 4 >> seconds that you might need to load the first list filter some more. >> >> Mark >> >> On Monday, June 26, 2017 at 4:44:45 PM UTC-7, Arlen Beiler wrote: >>> >>> Brilliant!!! Here is my test and result >>> >>> <<now "mm:0ss">> <-- 41:23 >>>> <$list filter="1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20"> >>>> <$list filter="[all[tiddlers+shadows]]"> >>>> <$list filter="[<currentTiddler>has[text]]"> </$list> >>>> </$list> >>>> </$list> >>>> <<now "mm:0ss">> <-- 41:27 (4 seconds) >>>> <$list filter="1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20"> >>>> <$list filter="[all[tiddlers+shadows]]"> >>>> <$list filter="[is[current]has[text]]"> </$list> >>>> </$list> >>>> </$list> >>>> <<now "mm:0ss">> <-- 41:31 (4 seconds) >>> >>> >>> Apparently no significant difference. >>> >>> >>> >>> On Mon, Jun 26, 2017 at 4:59 PM, @TiddlyTweeter <tiddly...@assays.tv> >>> wrote: >>> >>>> WHOAH! Is that a proto Test Suite? >>>> >>>> On Monday, 26 June 2017 22:15:13 UTC+2, Mark S. wrote: >>>>> >>>>> My informal test, running the code below on TiddlyWiki.com, suggests >>>>> that <currentTiddler> may be twice as fast as is[current]. Minutes and >>>>> seconds are posted at the top and bottom of the process loop for >>>>> comparison. >>>>> >>>>> <<now "mm:0ss">> >>>>> <$list filter="1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20"> >>>>> <$list filter="[all[tiddlers+shadows]]"> >>>>> <$list filter="[<currentTiddler>has[text]]"> >>>>> .</$list> >>>>> </$list> >>>>> </$list> >>>>> <<now "mm:0ss">> >>>>> >>>>> >>>>> >>>>> >>>>> On Sunday, June 11, 2017 at 8:31:32 AM UTC-7, Danielo Rodríguez wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> I was creating some template tiddlers when I suddenly discovered >>>>>> myself using <currentTiddler> a lot within list widgets. >>>>>> >>>>>> This is what was natural for me at that moment, but I just remembered >>>>>> that I before I normally use the filter operator [is[current]] or >>>>>> [all[current]] and the doubt appeared. Which one has better performance? >>>>>> Using the <currentTiddler> variable or the [is[current]] filter operator. >>>>>> >>>>>> For me makes sense that just accessing a variable is much more >>>>>> performant than just filtering all the tiddlers to see which one is the >>>>>> current one. One usage example is as follows: >>>>>> >>>>>> >>>>>> <$list filter="[<currentTiddler>has[text]]"> >>>>>> Text if the field exists >>>>>> </$list> >>>>>> <$list filter="[<currentTiddler>!has[text]]"> >>>>>> Text if the field does not exist >>>>>> </$list> >>>>>> >>>>>> >>>>>> Maybe there are situations where you want to use the filter version >>>>>> instead of the variable, but since both depend on the value of the >>>>>> current >>>>>> tiddler variable, I can't think of any situation like this. >>>>>> >>>>>> Any reasoning about this is very welcome. If currentTiddler is more >>>>>> performant for this base cases, I think it should be included as some >>>>>> part >>>>>> of good practices or something like this. >>>>>> >>>>>> Regards >>>>>> >>>>> -- >>>> 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+...@googlegroups.com. >>>> To post to this group, send email to tiddl...@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/ms >>>> gid/tiddlywiki/1dbc1104-1500-4409-a34b-401384cfcef6%40googlegroups.com >>>> <https://groups.google.com/d/msgid/tiddlywiki/1dbc1104-1500-4409-a34b-401384cfcef6%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 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/ms >> gid/tiddlywiki/70bd2ecd-1c52-4f06-a46d-bedf1d8a5371%40googlegroups.com >> <https://groups.google.com/d/msgid/tiddlywiki/70bd2ecd-1c52-4f06-a46d-bedf1d8a5371%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 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/CAJ1vdSRc6Qfs8YWH7g4r-q2yg05Uffem9z92uMGaNxpFUGx7JQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
