Compounded delay and accompanying lag

[yodxxx1]

Please complete the following information when submitting a feature request or bug report.

• Extension version: 7.1.6.2
• Browser name & version: Chrome 131.0.6778.205 (64-bit)
• Operating system & version: Windows 10 pro 19045.5247
  Even though I dont think the versions really matter since this problem has been appearing for some time now

I always have a lot of tabs open (often in the 1000s) in multiple windows (in total), and I have noticed some problems when it comes to the performance of tms, and secondary effects which are caused by the performance issues.

While everything is working perfectly fine with little cpu usage while all tabs which are supposed to be suspended are suspended, and all tabs which are supposed to be active are active, the moment i try to unsuspend multiple tabs, or try to load tabs from elsehwere which have been previously suspended (with something like recovering sessions or using onetab) there are major problems:
-In the case of the new tabs, they are blank pages until tms attempts to load them, and in the case of pages "flaged for suspension" (aka when I use the "suspend all" feature, or try to suspend a page when the extension is already struggling with the other issues) they do not get suspended for sometimes a long time period.
-In both of the above mentioned cases tms decides to only attempt to put like 10 pages at a time in the suspended mode, which for some reason often takes 5+ minutes, and then it goes to the next ~10 pages
-In bad cases where I try to suspend or load a lot of pages it often takes 2+ hours to have all the pages put into the suspended mode
-An additional problem with all of that is that this aparently puts a very high load on the cpu, causing my whole computer, but especially chrome to lag, making it pretty much unusable while all of those tabs are scejuled
-This lag problem also exists when I either try to suspend only 1 or a few tabs, or when the auto suspension feature kicks in... definitely not as bad because its only a few tabs max, so it only gives me a minute of lag, but its still notciable

I know im definitely stressing the extension with my high abount of tabs, but I have a good cpu in my pc which does not cause any lag issues with prettymuch anything else, I always have a lot of space left in my ram, and those problems also have only appeared at random, but then stayed ever since

Also I know that nothing is instant, but transfering the data of a link, and activating a black window for 10 tabs cant possibly take minutes... or even hours if you have some more

Additional info:

I have 48 gb of ram (increasing amount didnt change this problem), which always stays at roughly 30-40% usage, no mater what the extension is doing

My cpu maxes out during the attempt to suspend or load tabs into being suspended
Normally its at 5-20%
My cpu is a Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz 4.00 GHz

And this is either a bug report (in case this is a bug), or a feature request for making the extension more efficient if it isnt

[github-actions]

🇮🇹 Grazie per aver aperto la segnalazione. Ti informo, però, che il progetto è in fase di chiusura. Vedi #196.

🇬🇧 Thank you for opening the issue. Please be advised, however, that the project will soon be closed due to Chrome V3 manifest and new policies. Please take a look here: #196.

[Technetium1]

You are limited by 4 cores and Chromium's design. Browser allows as many tabs to queue for loading as you have cores rather than threads iirc. Hypothetical best case scenario, with 1000 tabs loading 4 per second (which is generous), is still going to take around 4.5 minutes. Have you tried to toggle the memory saver?

[yodxxx1]

You are limited by 4 cores and Chromium's design. Browser allows as many tabs to queue for loading as you have cores rather than threads iirc. Hypothetical best case scenario, with 1000 tabs loading 4 per second (which is generous), is still going to take around 4.5 minutes. Have you tried to toggle the memory saver?
@Technetium1

I heard of that saver feature when it first came out, but I tried to avoid it since i did not know if it would cause problems together with tms, and also I thought it was redundant if I already was using tms.
So is it safe to use together with tms and wont cause any strange issues?

On the topic of the speed... Id absolutely love to be able to load my 2000 tabs in something like 10 minutes (or even 20 would be fine), but currently it takes hours to load and lags everything out... I think one of the problems is also that it takes breaks between each group of tabs, so it suspends 5 for 10 minutes, finishes, waits another 5 minutes, and only then starts the next ones...
I remember when it could load a few tousand tabs in roughly the time you mentioned, also during that time it didnt lag anything out as much, so if it was still like that there wouldnt be any problem, but thats just not the case rn... for some reason it has become signifficantly slower and laggier at some point in the past

[Technetium1]

Unfortunately I migrated away from Chrome, so I can't confirm on current versions, but I was having a positive experience with memory saver enabled simultaneously. They seemed to compliment each other well, and did not cause any issues. I don't believe anything major would have changed regarding the implementation since ~September.

I don't prefer tab groups, so I never tested, but there have been various other issues reported over the last few months about them being slow or sometimes not working as expected. Just based off my experience reading those comments, I automatically lean towards blaming groups. Even more since you describe a delay between groups. Can you open Chrome's task manager when launching, and see that there's no other extension potentially interrupting the tab reloads?

[yodxxx1]

@Technetium1
I guess ill have to read myself a bit into tab groups and the crome taskmanager then xD
since those were never features I conciously used

[yodxxx1]

Ok I read myself into both
But didnt find use for the tab groups for me (at least rn, maybe in the future some day)
I have The chrome ramsaver on but it doesnt make a difference

Anyway, while recovering the suspended tabs once again I looked into the chrome task manager and made this screenshot

Nothing else seemed to be out of the ordinary (at least cpu usage and ram wise), but whenever the progress of suspending any tab or tabs takes place, the cpu usage of the "browser" and tmc (sorry for it being partially in german) both skyrocketing to either 100% or above 100% each, and the general cpu usage on my pc (according to the windows task manager) becomes 90-100%

In other words, the suspender causes both itself and the general browser to lag so much that both slow down to a crawl, and because of that slow speed they also take forever to finish, expanding the problem caused by the lag, because that lag affects the entire system

tldr on my information:
-I did the same thing with my pc as I did before
-The problem started appearing suddenly, and idk where it came from
-The problem is that the suspender makes itself and the browser use up all available resources while its actively suspending
-And because of no available resources everything slows down and starts laging
-And the lag causes the suspension progress to also slow down, which expends the amount of time the issue exists
-These problems appear both when either whe tabs get suspended, or when they are loaded into suspension from being just simple links
-Also (A thing I might have forgotten to mention before), everything related to the suspended is slow... whenever I click the "suspend tab button" (or suspend all others) it often takes at least 2 minutes per tab to start the suspension progress, where the tab first becomes white and unusable for a few minutes, and then suspended (btw that white status is the form in which the tabs enter the browser when imported through external measures). Even when clicking the suspender button in the extensions bar, it often takes a couple of seconds before the ui for the suspender appears

In other words, I think all my problems stem from the suspender for some reason being slow and using way too many resources cpu wise, but everything only after a certain time (which I sadly cant remember when that was), because I had the same habbits of opening, closing, and have tabs oepn in the 1000s before all of these problems appeared, and while it took a few minutes to load then it didnt lag the pc out and it only took like 10 minutes at most

And I already tried running chrome with less tabs, but that only solved the problem halfway. While it definitely reduced the time it took for all to load, it did not fix the problem of every single suspension still taking forever and lagging everything out

@Technetium1 have done my research and problem assumption now

[Technetium1]

Seems that you have taken almost all the appropriate steps in troubleshooting this. I don't think it should be using so much memory, even for a large session, that seems strange. The last point is also unusual (taking 2+ min to suspend a tab manually), because it should begin almost instantly even on a slow machine.

The final easy troubleshooting is testing in a new browser profile, in the case something from the current one is corrupted somehow. If it's smooth, re-add your other extensions and see if it degrades after, could be some incompatibility that isn't obvious.