Live data from Hacker News

Chrome will aggressively throttle background tabs

blog.strml.net

211–220 of 403 posts

Re: Chrome will aggressively throttle background tabs

#211
post #196

Earlier quoted context omitted.

Pinning a tab should disable throttling. Gives user straightforward control over which tabs are important.

Not the greatest solution, considering Pinning isn't documented anywhere and most Chrome users have no idea it exists. Which is a shame, as pinning is probably my favorite browser feature.

Including me, thanks for the tip! First time I've ever heard of this feature.

Re: Chrome will aggressively throttle background tabs

#212

Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…

If a page signals it's desire to opt-out of aggressive throttling, the user should be notified of this, perhaps by an icon in the tab, so that we can either close it or force the throttling.

I'm a laptop user and CPU-hungry background tabs are a huge drain on my battery life. If something is opting out of or otherwise excluded from throttling, I want to know about it.

Thanks.

Re: Chrome will aggressively throttle background tabs

#213
post #77

Earlier quoted context omitted.

> They're not users. They're the blight on the back of users. Why cater to them? actually they are about 90%+ of users https://www.nngroup.com/articles/computer-skill-levels/

Fine, and most "webmasters" are really just hack frauds. On my planet, it's their job to get a room and ours to burn it. edit: Usage implies intentionality. Intentionality implies awareness. Not being some super guru, but more awareness than "is text, won't read". Therefore, while the drive to shovel hardware on people, to create needs you then get to fill, did indeed bring all sorts of people who now get called user…

This sounds a lot like the arguments in the 80s about how GUIs were bad because they let anyone use a computer. Empathy makes it easier to write good software.

Re: Chrome will aggressively throttle background tabs

#214

Earlier quoted context omitted.

Tree Style Tabs is a nice idea, but I found the balance of aesthetic and speed for me to be with pressing Ctrl+L and then inputting a few letters relating to the open tab I seek, then just pressing Enter and switching to the tab.

How do you get this feature? I know I've seen it, but it's not doing it on Mac Chrome.

Firefox. Maybe chrome has it as well, but Firefox does look like Chrome if you're not looking closely these days.

Re: Chrome will aggressively throttle background tabs

#215
post #196

Earlier quoted context omitted.

Pinning a tab should disable throttling. Gives user straightforward control over which tabs are important.

Not the greatest solution, considering Pinning isn't documented anywhere and most Chrome users have no idea it exists. Which is a shame, as pinning is probably my favorite browser feature.

>Not the greatest solution, considering Pinning isn't documented anywhere and most Chrome users have no idea it exists. -- I might say this is precisely why it'd be smart mode of control: Tying a power user-ish granular feature (throttling) to another power user feature (pinning) seems like a bit of self-selective optimization, while being quite elegant in its simplicity.

So, for me, +1 for pinned tabs != throttled.

Re: Chrome will aggressively throttle background tabs

#216
post #196

Earlier quoted context omitted.

Pinning a tab should disable throttling. Gives user straightforward control over which tabs are important.

Not the greatest solution, considering Pinning isn't documented anywhere and most Chrome users have no idea it exists. Which is a shame, as pinning is probably my favorite browser feature.

I'd use Pinning a lot more if it didn't shrink the tab down to its Favicon size. Wish it would also prevent you from closing the tab.

Re: Chrome will aggressively throttle background tabs

#217

Earlier quoted context omitted.

A common use-case is tabs that are streaming music. I'm not sure if most users are even aware of pinned tabs.

It still drives me nuts there's no keyboard shortcut for it. `Command + Shift + P` would be sweeeeeeet.

It is silly to need an extension for this, but I don't know what I would do without `Command + Shift + X`

https://chrome.google.com/webstore/detail/tab-pinner-keyboar...

Re: Chrome will aggressively throttle background tabs

#218
This is of course a really good thing, but I feel this is not enough.

The browser has increasingly become universal platform. On the one hand, this means applications written for browsers are automatically cross platform. But this also makes the browsers more and more complicated. Even the simplest webpage takes a significant hit in resource usage.

Maybe we need some sort of "reduced web". A browser that only supports the essential features to display webpages. No WebGL, canvas, notification, WebRTC, locations, WebMIDI, or WebUSB (seriously!). And I don't mean just disable these features, but rather design the browser without them. Then we could do most of our browsing in the minimal browser, and only fire up chrome for the more demanding web apps.

Re: Chrome will aggressively throttle background tabs

#219

Hi, this is Alexander. I'm an engineer on Chromium team working on scheduling and on background tab throttling in particular. Firstly, I want to make clear that we are not shipping this in Chrome 56. We have enabled throttling as an experiment in beta channel to measure impact and collect feedback from web devs. We will aim to ship it in Chrome 57, subject to further feedback. In response to concerns voiced we will d…

> In response to concerns voiced we will disable aggressive throttling when active websocket connection is present. Tabs playing audio are already unthrottled.

The pages that are most aggressive in being a drain on resources, in my experience, are also using websockets to constantly load in new advertising and JavaScript and other garbage. Just "the page has a WS open" should not be enough to keep a page unthrottled without providing the user a chance to change that behavior.

Re: Chrome will aggressively throttle background tabs

#220
post #216
post #196

Earlier quoted context omitted.

Not the greatest solution, considering Pinning isn't documented anywhere and most Chrome users have no idea it exists. Which is a shame, as pinning is probably my favorite browser feature.

I'd use Pinning a lot more if it didn't shrink the tab down to its Favicon size. Wish it would also prevent you from closing the tab.

Interestingly, I'd never use pinning if it didn't shrink the tab down. I never have any trouble with keeping my tabs ordered, so the main value pinning gives me is the shrinking.
Post reply on HN