lazy loading behavior tweaks

33 views
Skip to first unread message

FH

unread,
Jun 15, 2024, 6:13:39 PM (5 days ago) Jun 15
to Session Buddy Discussion
With lazy loading disabled through the new flag, the performance is significantly worse than it was in version 3. Indeed, in the latter, 7 years worth of past sessions were loaded in about 3 seconds. In version 4, this takes roughly 20 seconds. In addition, the whole interface becomes extremely sluggish. Search input is very laggy and the tab lists are slow to load when navigating between sessions. Also, after performing a search and clearing the search string, the entire saved collections list is loaded from scratch (for another 20 seconds).

Is there no way to simply restore version 3's behavior when disabling lazy loading through the experimental flag?

By the way, are the flag settings persistent or do they have to be set whenever the browser is restarted?

Thank you,

FH

Session Buddy Support

unread,
Jun 16, 2024, 8:31:30 AM (4 days ago) Jun 16
to sessionbud...@googlegroups.com
Flags are persistent.

That level of performance is expected at a few thousand collections. V3 was vanilla JS with Web SQL Database (vs React/IndexedDB), so fundamentally a different beast. There are alternative optimization opportunities worth exploring (most notably virtualization), but they come with their own costs.

Hans

--
You received this message because you are subscribed to the Google Groups "Session Buddy Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sessionbuddy-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/421cf30c-6ad6-48e6-9dee-0c4f6f647177n%40googlegroups.com.

john s wolter

unread,
Jun 18, 2024, 1:40:42 AM (2 days ago) Jun 18
to sessionbud...@googlegroups.com
What kind of virtualization would be used?

Cheers, John S Wolter, Johnny 10-Shots, Staying Safe, Immune Challenged, Remote/Hybrid Okay

john s wolter

unread,
Jun 18, 2024, 5:08:17 AM (2 days ago) Jun 18
to sessionbud...@googlegroups.com

Looking at the current "Post Repair" screen picture there aren't any Collections.  I have used SB since the last repair.  All Collections were removed at that time too.

Therefore the Chrome update extension repair reinstalled SB.  This installed blank databases as expected.  This likely is similar yet not the same as the SB V3 to V4 conversion.  How are these two processes different?  Why were most database conversions successful while a minority lost data?

This is unlikely to be the only fix needed.  More errors are lurking inside all the parts and pieces making up SB and all other software and any kind of systems.

Keep looking for other problems.

Cheers, John S Wolter, Johnny 10-Shots, Staying Safe, Immune Challenged, Remote/Hybrid Okay
Chrome-Post-updating-127-0-6533-5.7z
IndexedDB-Pre-Repair.7z

Session Buddy Support

unread,
Jun 18, 2024, 6:39:26 AM (2 days ago) Jun 18
to sessionbud...@googlegroups.com
Look up "virtual scrolling"

Hans


On Tue, Jun 18, 2024 at 5:40 AM john s wolter <johns...@wolterworks.com> wrote:
What kind of virtualization would be used?

Cheers, John S Wolter, Johnny 10-Shots, Staying Safe, Immune Challenged, Remote/Hybrid Okay

--
You received this message because you are subscribed to the Google Groups "Session Buddy Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sessionbuddy-dis...@googlegroups.com.

Session Buddy Support

unread,
Jun 18, 2024, 7:14:21 AM (2 days ago) Jun 18
to sessionbud...@googlegroups.com
Side note, we use virtual scrolling in the search result dropdown.

Hans

Reply all
Reply to author
Forward
0 new messages