PLEASE reduce the cpu load when recovering tabs!!

[james joe]

I have a lot of tabs open when I use session buddy, and upon restoring two groups of tabs, I hit 100% CPU utilization BOTH TIMES! I think it should not be doing that just for reopening tabs, it certainly didn't do that on  V3.

[Session Buddy Support]

The factors that contribute to CPU load are pretty complex. Among other things that are difficult to control for, it's dependent on the pages you're loading, the state of their caches, what Chrome decides to prioritize, available disk space, and whatever else your system is currently doing.

Nothing in v4 has changed with respect to how tabs are opened except that it will now actually do LESS work above a particular tab count threshold.

Hans

On Sat, Mar 16, 2024 at 12:05 PM james joe <creeperk...@gmail.com> wrote:

I have a lot of tabs open when I use session buddy, and upon restoring two groups of tabs, I hit 100% CPU utilization BOTH TIMES! I think it should not be doing that just for reopening tabs, it certainly didn't do that on  V3.

--
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/d02e67ff-1ec2-415d-958e-cab7cdb9797bn%40googlegroups.com.

[Mohammad Noor]

"Nothing in v4 has changed with respect to how tabs are opened"

Tabs now open one by one, that is completely different from before when i'd be able to load everything up at once. Going each tab at a time takes so much time when loading up thousands of tabs. 

[Melody Nelson]

Multiple (I think I saw 3-4 mentions before) people had complained about slow opening/CPU load of v4 tabs. Possibly the new spacing out delay feature makes the opening feel slower? And can the discard algorithm in theory use more CPU than the normal opening, at least under specific circumstances?

If it won't be possible to optimize both RAM and CPU usage (until Chrome implements launching tabs as natively discarded in the extension API) soon, maybe a choice between the two should be offered in the Settings? At least as a dev build for testing purposes for those who have those CPU issues.

People with a lot of RAM and/or not a lot of tabs might appreciate it, especially on older CPUs. There might be cases when with the RAM optimization disabled the browser will be crashing due to out of memory. In case SB is able to detect a crash after opening a lot, on the restart it could offer to enable RAM optimization.

[Mohammad Noor]

Adding an option to go back to v3 restore would be nice. It takes so much longer now to restore thousands of tabs vs before it would more efficient for me to restore thousands by doing 1-2 windows at a time.

[Session Buddy Support]

> Tabs now open one by one, that is completely different from before when i'd be able to load everything up at once. Going each tab at a time takes so much time when loading up thousands of tabs.

OK sure, but the open call itself hasn't changed.

Tab open optimization was tested extensively and introducing a delay had the effect of dramatically minimizing CPU load across the time it takes to fully load many tabs. The  primary intent of the delay is to minimize the chance of a browser crash, which is something that many people were reporting. I'm sure there are ways to optimize this further (eg, dynamic delay threshold and duration).

Based on feedback, the default threshold for when optimizations kick in has been bumped up from 30 tabs to 60 in v4.0.2.

If you want to tweak this, you can use the "experiments" feature by adding either of the following localStorage entries:

nxs.experiment.optimized-open-delay : <number of ms to delay each open, kicks in after threshold number of tabs have been opened, default 100>

nxs.experiment.optimized-open-threshold : <number of tabs opened after which delay and suspending optimizations kick in>

Hans

To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/3d6a3878-515f-48c4-b18e-98a67a523cf9n%40googlegroups.com.

[Session Buddy Support]

>  can the discard algorithm in theory use more CPU than the normal opening, at least under specific circumstances?

We did test this extensively and it consistently led to dramatically lower CPU usage but I suppose the multivariate nature of it makes it possible.

> maybe a choice between the two should be offered in the Settings

Sure we could possibly surface these tweaks in settings at some point.

Hans

To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/84153dc3-2d1c-437a-aa24-91a500b53f08n%40googlegroups.com.

[David Morris]

Is it not possible to replicate the lazy load feature of Chrome itself? When I open Chrome, it restores all several hundred tabs previously opened, virtually instantly. I can immediately start browsing and switching tabs without any performance hit. Because it doesn't actual load the tab contents until I hover over a tab or open the tab. I don't know if Chrome exposes this capability to extensions, but that would be the behavior I'm looking for. Loading hundreds of tabs under v3 was extraordinarily painful as it brought my computer to its knees for 5-10 minutes while it loaded every single tab. I was hoping that v4 was able to tap into the same lazy load feature that Chrome uses. From what I'm reading, v4 still completely loads every tab, just with a delay between each one. I haven't stress tested this in v4 yet, but while it may be less painful than v3, it doesn't sound like it compares to the native Chrome lazy load feature.

David

[Melody Nelson]

> I don't know if Chrome exposes this capability to extensions

It does not, see https://issues.chromium.org/issues/41411256

Which is why every extension has to implement a custom solution for this for now.

[David Morris]

Thanks. Unfortunately that request is over 4 years old. It does look like it was bumped last month, so I added my $0.02 to it.

You received this message because you are subscribed to a topic in the Google Groups "Session Buddy Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sessionbuddy-discuss/z9Zs8Q0R05g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sessionbuddy-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sessionbuddy-discuss/a35189f6-8597-4032-96fe-7383197784f4n%40googlegroups.com.

[Session Buddy Support]

FWIW, v4.0.3 disables tab opening optimizations by default. A setting has been added to enable them (under Settings > Tabs).

https://sessionbuddy.com/release-4-0-3/

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/42a2d8a9-97f7-4620-9afa-e14c83813db1n%40googlegroups.com.