4 ms·

Ctrl+tab'd thru all 56 tabs in this group, waited for them to finish loading, opened activity monitor: CPU at 20%, RAM at 811MB. So yea, a fair amount weren't l

Ctrl+tab'd thru all 56 tabs in this group, waited for them to finish loading, opened activity monitor: CPU at 20%, RAM at 811MB. So yea, a fair amount weren't loaded, but loading them didn't make too big of a difference.

nothrabannosir 10y ago
CPU at 20%, "loading didn't make too much of a difference"??? 20% is obscene for a process without interaction. Imagine a paused video player taking 20%, or a minimised word editor. Even at 58 videos or documents.
- syrrim 10y ago
  You forget that webpages are allowed to do what ever the hell they want, and so each is probably running a script or two in the background. We put up with a lot in webapps that would never stand in a desktop app.
  - jbergens 10y ago
    I never used to start 100+ normal apps. It would have dragged my old computers to a crawl.
  - MustardTiger 10y ago
    This is a huge problem. Javascript has become a blight on the web, and browsers really need to make it easier to manage stopping scripts on background tabs and such.
  - nothrabannosir 10y ago
    I don't forget, I just don't forgive. It's unacceptable either way. Someone has to take responsibility---might as well start with the browser. Then we can push it down from there; maybe if browsers were held accountable for pages' resource usage they'd implement resource controls. Like they currently do with limiting setTimeout on inactive pages, but more comprehensively. And maybe they'd implement better inspection tools for resource usage (chrome was ahead of the game; I'm looking at you, Firefox )
    - bzbarsky 10y ago
      > Like they currently do with limiting setTimeout on inactive pages, but more comprehensively. Firefox is working on this. Doing it without breaking things like music streaming sites is ... delicate.
  - Senji 10y ago
    Maybe tabs not currently being viewed should have their JS throttled? Is this an option in FF yet?
    - reitanqild 10y ago
      I use Suspend Tab. Earlier this year I realized a major offender was Google search and search results pages which would spin up a core more than once a minute. This explained to me at least why it was still hogging cpu even with ad blocker.
    - nicoburns 10y ago
      Not yet, but they're working on it: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-project/ https://billmccloskey.wordpress.com/2016/10/27/mozillas-quan... and a preliminary version of this feature is in Chrome 56: https://www.chromestatus.com/features/5701844080787456 https://www.chromestatus.com/features/5701844080787456
    - nicoburns 10y ago
      Not yet, but they're working on it: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-project/ https://billmccloskey.wordpress.com/2016/10/27/mozillas-quan...
    - nicoburns 10y ago
      Not yet, but they're working on it: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-project/ https://billmccloskey.wordpress.com/2016/10/27/mozillas-quan... and a preliminary version is in Chrome 56: https://www.chromestatus.com/features/5701844080787456 https://www.chromestatus.com/features/5701844080787456
    - drkstr 10y ago
      Use requestAnimationFrame instead of setTimeout to get a throttled heartbeat.
EpicEng 10y ago
Well hell, maybe it's time for me to look at FF again. I switched away because it was a memory hog... And now chrome's a memory hog. I read that they made improvements, but 800MB for 240+ tabs is pretty good.

nothrabannosir 10y ago

CPU at 20%, "loading didn't make too much of a difference"??? 20% is obscene for a process without interaction. Imagine a paused video player taking 20%, or a minimised word editor. Even at 58 videos or documents.

syrrim 10y ago
You forget that webpages are allowed to do what ever the hell they want, and so each is probably running a script or two in the background. We put up with a lot in webapps that would never stand in a desktop app.
- jbergens 10y ago
  I never used to start 100+ normal apps. It would have dragged my old computers to a crawl.
- MustardTiger 10y ago
  This is a huge problem. Javascript has become a blight on the web, and browsers really need to make it easier to manage stopping scripts on background tabs and such.
- nothrabannosir 10y ago
  I don't forget, I just don't forgive. It's unacceptable either way. Someone has to take responsibility---might as well start with the browser. Then we can push it down from there; maybe if browsers were held accountable for pages' resource usage they'd implement resource controls. Like they currently do with limiting setTimeout on inactive pages, but more comprehensively. And maybe they'd implement better inspection tools for resource usage (chrome was ahead of the game; I'm looking at you, Firefox )
  - bzbarsky 10y ago
    > Like they currently do with limiting setTimeout on inactive pages, but more comprehensively. Firefox is working on this. Doing it without breaking things like music streaming sites is ... delicate.
- Senji 10y ago
  Maybe tabs not currently being viewed should have their JS throttled? Is this an option in FF yet?
  - reitanqild 10y ago
    I use Suspend Tab. Earlier this year I realized a major offender was Google search and search results pages which would spin up a core more than once a minute. This explained to me at least why it was still hogging cpu even with ad blocker.
  - nicoburns 10y ago
    Not yet, but they're working on it: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-project/ https://billmccloskey.wordpress.com/2016/10/27/mozillas-quan... and a preliminary version of this feature is in Chrome 56: https://www.chromestatus.com/features/5701844080787456 https://www.chromestatus.com/features/5701844080787456
  - nicoburns 10y ago
    Not yet, but they're working on it: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-project/ https://billmccloskey.wordpress.com/2016/10/27/mozillas-quan...
  - nicoburns 10y ago
    Not yet, but they're working on it: https://billmccloskey.wordpress.com/2016/10/27/mozillas-quantum-project/ https://billmccloskey.wordpress.com/2016/10/27/mozillas-quan... and a preliminary version is in Chrome 56: https://www.chromestatus.com/features/5701844080787456 https://www.chromestatus.com/features/5701844080787456
  - drkstr 10y ago
    Use requestAnimationFrame instead of setTimeout to get a throttled heartbeat.

EpicEng 10y ago

Well hell, maybe it's time for me to look at FF again. I switched away because it was a memory hog... And now chrome's a memory hog. I read that they made improvements, but 800MB for 240+ tabs is pretty good.