I& #39;ve all but confirmed that it& #39;s specifically the @linkedin web page (that I had kept pinned in my chrome-for-windows) which was chewing up about 40% of my battery life. I closed everything and re-opened all but that, still normal battery draw. Here is the site idle at CPU 15.6%!
the @linkedin tab seems to only be doing some network traffic while as a background tab, so it only occasionally is spiking the CPU, the rest of the time sitting at 0%.

but as soon as I activate the tab, its CPU jumps up to around 10%, and constantly bounces between 8 and 25%.
how could the site possibly be consuming 10-25% of my CPU at all times that the tab is active?

I mean, cliche, we say "oohhh, shitty JS and SPA sites". but no, like, seriously, how could you possibly be so poorly written to consume that much CPU?
the @linkedin site is built on ember... in fact a number of their core devs work there, and they& #39;re a primary incubator/supporter of the framework.

one would presume this site is built somewhat "to spec" of how an ember site should be.

if so, that& #39;s horrifying.
If I wrote a super naive framework that re-rendered the whole page constantly, churning the DOM and everything, causing tons of GC thrashing, etc.... I& #39;m still not sure if I could get it to consistently kill 10-25% of the CPU, constantly, just never ending.
if I was like rendering the entire web page in webgl and rotated in 3d, re-rendered 60fps, and did everything I could to avoid being able to have GPU acceleration, I am not sure if I& #39;d chew through 10-25% CPU.
I& #39;m just sorta stunned. I never could have guessed/admitted/accepted that one single web page could be the culprit of my laptop having literally HALF it& #39;s advertised battery life... ~4-5 hours instead of 9-10.
here& #39;s the worst part... I actually really like @linkedin, and I use it quite often throughout my day. It& #39;s my secondary social network after this one.

I& #39;m not shitting on it because I want to make fun of them. I& #39;m genuinely sad that I can no longer justify having it open.
By contrast, I& #39;m actively using twitter right now, installed PWA (chrome). I& #39;m watching the chrome task manager, and seeing approx 1-3% CPU consistently being used while I& #39;d writing these tweets.

Again, comparison was @linkedin just sitting there (idle foreground) at 10-25% CPU.
You can follow @getify.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled: