@benthompson flash is certainly egregious, but a while back Chrome made decisions to optimize performance, prefetch, etc - comes at a cost
-
-
Replying to @johnolilly
@johnolilly@benthompson Not prefetch. WebKit and Safari started prefetching the same time as Chrome. It was done in WebKit before the fork.1 reply 0 retweets 1 like -
Replying to @xeenon
@xeenon@benthompson yes, that’s right - they also aggressively instantiate objects, etc.1 reply 0 retweets 0 likes -
Replying to @johnolilly
@johnolilly@benthompson Sounds like the wrong kind of optimization. Safari isn’t slow by any measure, and we still get good battery life.1 reply 0 retweets 1 like -
Replying to @xeenon
.
@johnolilly@benthompson:@xeenon is right. This is all scheduling and graphics stack. OS X power use in graphics is hard to reason about.2 replies 0 retweets 2 likes -
Replying to @slightlylate
@johnolilly@benthompson@xeenon : several different ways to draw, massively different power characteristics. Chrome is switching method1 reply 0 retweets 0 likes -
Replying to @slightlylate
@johnolilly@benthompson@xeenon : for context, FF uses the same power-hungry GL paths Chrome does today4 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate Which power-hungry GL paths do you mean?1 reply 0 retweets 0 likes -
Replying to @muizelaar
@muizelaar : from what (little) I understand, OS X's GL drawing infra requires full upload every frame, very power hungry2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate Can it be avoided and if so how?2 replies 0 retweets 0 likes
@muizelaar : we're still trying to understand entirely. Chris Cameron is doing that work; follow his crbug contributions.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.