Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome will aggressively throttle background tabs

blog.strml.net

Post reply on HN
Print view View original

151–160 of 403 posts

Re: Chrome will aggressively throttle background tabs

#151

Post by DamnInteresting »

mcescalante wrote: post #8

It's awesome to see Chrome trying to improve performance for people with many tabs open, which is many of us. I use a LOT of tabs, and the best plugin has been The Great Suspender. Highly recommend it for anyone who wants memory & CPU back and keeps many tabs/windows open at once: https://chrome.google.com/webstore/detail/the-great-suspende...

The combo of The Great Suspender + Session Buddy makes tab management so much better, and easier on resources.

Leave open the tabs you know you'll need soon(ish) and let the Great Suspender throttle them, and save (then close) groups of tabs/windows you won't need right away using Session Buddy.

https://chrome.google.com/webstore/detail/session-buddy/edac...

Re: Chrome will aggressively throttle background tabs

#152

Post by rhizome »

pmiller2 wrote: post #66
josu wrote: post #48

Earlier quoted context omitted.

Or just ask for the permission when you first open the page, the same way uber asks for your location. www.foobar.com wants to: "Run in the background unthrottled"

That's less "backward compatible" than the suggestion to pop up a dialog on switching to the page, because the page needs to know to ask for the permission. I'm not sure if that's a good thing or a bad thing. After all, backward compatibility is how we got the semantics of an alert() dialog stopping all JS execution.

These days, due to my annoyance with pages reloading themselves when switching to a tab, I'm really not interested in packing more functionality into the whole tab switching mechanism. Like the back button, it should not be visible to web developers.

Re: Chrome will aggressively throttle background tabs

#153

Post by rhizome »

PetahNZ wrote: post #139
onion2k wrote: post #112

Earlier quoted context omitted.

As a developer you need to decide whether or not to support a browser, and if that browser doesn't provide the APIs you need then you should drop support for that feature in that browser. In this case, if Chrome is making a change that you can't or won't change your game for then the solution is to detect Chrome and display a "This game only works in a single tab in Chrome. Try Firefox!" message if a user opens it in…

It's your customers that generally dictate what browser you support.

If you don't support a browser, how do you learn whether its users are your customers?

Re: Chrome will aggressively throttle background tabs

#154

Post by TeMPOraL »

drinkjuice wrote: post #50

How about displaying more info about the "weight" of a page, when it comes to downloaded assets, cookies / local storage, RAM and CPU usage? I know there are ass backwards and fugly ways to see all of that, but why can't I see a list of all open tabs, with columns of such info which I get to define and sort as I please? Why not have the option to that info pop up when hovering over a tab, and to show notification ico…

What I'd like is popping up plain warnings aimed at regular, non-tech user. "These tabs are currently slowing down your computer: ." Or, "This tab uses a lot of battery power."

Besides directly providing information that is relevant to a typical user, I'd hope such a solution would finally put some pressure on the companies to optimize their webpages.

Re: Chrome will aggressively throttle background tabs

#155

Post by bsg75 »

mcescalante wrote: post #8

It's awesome to see Chrome trying to improve performance for people with many tabs open, which is many of us. I use a LOT of tabs, and the best plugin has been The Great Suspender. Highly recommend it for anyone who wants memory & CPU back and keeps many tabs/windows open at once: https://chrome.google.com/webstore/detail/the-great-suspende...

Any experience on how it compared to The Great Discarder from the same dev? https://chrome.google.com/webstore/detail/the-great-discarde...

Re: Chrome will aggressively throttle background tabs

#156

Post by blauditore »

baby wrote: post #120
blauditore wrote: post #110

Earlier quoted context omitted.

I meet many tab hoarders (always open a new one, never close any, ending up with hundrets), but just can't wrap my head around it! I hate having more than 6-7 simultaneously open because it gets increasingly harder to keep an overview of what you're doing. The same applies for IDE tabs or windows. Too much of them and finding the right one becomes increasingly hard, and losing the thread more likely.

Not if you use Tree Style Tabs. I've been using it for years and I have no idea how other people can efficiently browse the web without it.

Hmm, looks interesting. I've tried out several tools for organizing tabs, but none of them really worked as well as aggressive manual "garbage collection" for me. Usually the problem was that switching between groups (or whatever concept) was too complicated, or part of the tabs were hidden too much. Maybe I should give this one a try.

Re: Chrome will aggressively throttle background tabs

#157

Post by mikeash »

valarauca1 wrote: post #150
mikeash wrote: post #109

Earlier quoted context omitted.

"This is a data interpretation problem." That's what I said. "Defining it is what's hard." You seem to understand what I'm saying, and agree with me, but insist on arguing for some reason I cannot comprehend.

You seem to understand what I'm saying and agree with me Literally the opposite. Your initial statement was Measuring memory usage is hard on a modern OS. Which you've agreed was false as /proc/$PID/maps is easy to read. Then said: Defining it is what's hard But these statements are not mutually inclusive nor does the later imply the former. I stated measuring is literally the simplest thing. You said ah but what you…

Nooooo... somebody else made that initial statement. My initial statement was "Measuring it is easy. Defining it is what's hard."

Are you just arguing with me because you didn't realize I was somebody else?

Re: Chrome will aggressively throttle background tabs

#159

Post by rhizome »

dejawu wrote: post #80
drinkjuice wrote: post #50

How about displaying more info about the "weight" of a page, when it comes to downloaded assets, cookies / local storage, RAM and CPU usage? I know there are ass backwards and fugly ways to see all of that, but why can't I see a list of all open tabs, with columns of such info which I get to define and sort as I please? Why not have the option to that info pop up when hovering over a tab, and to show notification ico…

It's not everything you asked for, but as it stands Chrome does have a task manager (Shift + Esc) that shows CPU usage, Memory, and also how the tabs are grouped process-wise.

By the by, why we can't switch to a tab from the task manager is a question for the ages.

Re: Chrome will aggressively throttle background tabs

#160

Post by Kiro »

rdsubhas wrote: post #92
jklinger410 wrote: post #78

Earlier quoted context omitted.

Pinned tabs would be an easy solution for this. "Don't throttle pinned tabs"

While this is elegant, its still dangerous. There are online payments that could check whether your booking is complete in the background by periodically firing ajax calls, bulk updates or uploads, etc.

How is that relevant to throttling?
Post reply on HN