Live data from Hacker News

Do more with Chrome on a single charge on MacBooks

blog.chromium.org

11–20 of 35 posts

Re: Do more with Chrome on a single charge on MacBooks

#11
post #10

Can someone explain to me how I'm supposed to develop an Enterprise web app, that requires a regular "liveliness" check-in and to continue to receive timely notifications without internet access (internal only)? Between all the creative ways they're finding to decide they should throttle a tab or put it to sleep, and the ways they keep screwing with timers/intervals, I feel like I'm being forced back to pushing for a…

Web Push?

https://web.dev/notifications/

Re: Do more with Chrome on a single charge on MacBooks

#12
post #10

Can someone explain to me how I'm supposed to develop an Enterprise web app, that requires a regular "liveliness" check-in and to continue to receive timely notifications without internet access (internal only)? Between all the creative ways they're finding to decide they should throttle a tab or put it to sleep, and the ways they keep screwing with timers/intervals, I feel like I'm being forced back to pushing for a…

genuine question, why not write a desktop app instead?

Re: Do more with Chrome on a single charge on MacBooks

#13
post #10

Can someone explain to me how I'm supposed to develop an Enterprise web app, that requires a regular "liveliness" check-in and to continue to receive timely notifications without internet access (internal only)? Between all the creative ways they're finding to decide they should throttle a tab or put it to sleep, and the ways they keep screwing with timers/intervals, I feel like I'm being forced back to pushing for a…

There's a way to cheat and keep persistent timers ticking (albeit at a reduced rate) for longer, but if I describe how it works online they'll fix it :) The timer throttling algorithm(s) are documented.

Make a desktop/mobile app, unfortunately. Web platform people don't want your app.

Re: Do more with Chrome on a single charge on MacBooks

#14
post #11
post #10

Can someone explain to me how I'm supposed to develop an Enterprise web app, that requires a regular "liveliness" check-in and to continue to receive timely notifications without internet access (internal only)? Between all the creative ways they're finding to decide they should throttle a tab or put it to sleep, and the ways they keep screwing with timers/intervals, I feel like I'm being forced back to pushing for a…

Web Push? https://web.dev/notifications/

I have never once consented to a "let me send you notifications" request from a website, so this seems like a bad solution. They're widely abused by random trashy websites so it seems like it would be hard to get end users to consent so your app can use them to avoid timer throttling.

Re: Do more with Chrome on a single charge on MacBooks

#16

>In our testing, we found that you can browse for 17 hours or watch YouTube for 18 hours I'm quite interested in how YouTube can give more hours than browsing. Is it due to the bloat of modern webpages or something else?

If the user is watching YouTube, the system is spending most of its non-idle time downloading chunks of video, shoveling them into the decoder, and piping the output to the screen. This is a heavily hardware-accelerated workflow, and is quite efficient. The structure of the YouTube web app helps, too; it's a (well disguised) single-page app, so the browser doesn't even have to reload/reparse scripts when navigating from one video to another.

Browsing web pages is much more chaotic. As the user scrolls through the page, the system is having to render parts of the page (on the CPU), evaluate CSS rules, run scripts... the works. When the user navigates to a new page, that's a whole bunch of new HTML, CSS, and scripts that have to be parsed. And so on.

Re: Do more with Chrome on a single charge on MacBooks

#17

>In our testing, we found that you can browse for 17 hours or watch YouTube for 18 hours I'm quite interested in how YouTube can give more hours than browsing. Is it due to the bloat of modern webpages or something else?

If the user is watching YouTube, the system is spending most of its non-idle time downloading chunks of video, shoveling them into the decoder, and piping the output to the screen. This is a heavily hardware-accelerated workflow, and is quite efficient. The structure of the YouTube web app helps, too; it's a (well disguised) single-page app, so the browser doesn't even have to reload/reparse scripts when navigating f…

I think a big part of it is just the smooth scrolling. On my iPhone, I can see power draw double as I scroll. (My charger displays this).

I remember having to disable smooth scrolling when I had a computer barely capable of playing mp3s.

Re: Do more with Chrome on a single charge on MacBooks

#18

> In our testing, we found that you can browse for 17 hours or watch YouTube for 18 hours on a MacBook Pro (13", M2, 2022) Compared to which numbers before the update?

"According to Apple's specifications, the MacBook Pro 13 (2022) can provide up to 20 hours of Apple TV movie playback and up to 17 hours of wireless web browsing."

Interesting. Looks like Chrome just fixed energy issues with their app to keep up with Safari?

Anyway, they don't say anything about brightness and number before fixes, yeah.

Re: Do more with Chrome on a single charge on MacBooks

#19
> We identified data structures in which there were frequent accesses with the same key and optimized their access pattern.

What does this mean? The image implies the use of some sort of associative data structure implemented by linear search. But no one does that.

Post reply on HN