On Tuesday, October 13, 2020 at 8:20:53 AM UTC-7, Eric Shulman wrote: > > Yes. This does tend to slow things down. There's probably a few things I > can try to help reduce the processing overhead for "Timeline" handling when > there are lots of dates involved. One possibility is to limit the > generation of Timeline Events to only match the current year. >
PERFORMANCE UPDATE! getevents() now takes params "yyyy" and "mm" which are passed down to getevents_listed(), getevents_ics(), getevents_timeline_annual(), and getevents_timeline_range() These macros now only return events that match the specified "yyyy" and "mm" values. This reduces the processing load for each month by about 50-60% because the showday() macro no longer has to filter through ALL events. This is particularly true when testing with the "Science Timeline" enabled, which adds over 300 events to the calendar (birthdays for Marie Curie, Albert Einstein, Carl Sagan, and Neil deGrasse Tyson). Before the performance improvements, displaying a yearly calendar with all events enabled took about 4-5 seconds. It now takes about 2 seconds! Note that in the "view all events" list in Calendar Settings, it still shows ALL enabled events. This is because it invokes getevents() without any YYYY and MM values, so the filters simply default to matching all dates. Anthony: please get the latest update from http://tiddlytools.com/timer.html and let me know how it goes... enjoy, -e -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ef20ee77-51cd-417a-ac96-ba713cc59892o%40googlegroups.com.
