Live data from Hacker News

A new speed milestone for Chrome

blog.chromium.org

131–140 of 161 posts

Re: A new speed milestone for Chrome

#131
post #93

Earlier quoted context omitted.

You'd be surprised (I was), but high memory usage is also a power drain.

That sounds unlikely since DRAM is all refreshed constantly regardless of whether or not it is being used. Perhaps you meant storing and fetching from memory lots impacts battery life?

With higher memory usage you have less free memory for caching so you hit the disk/SSD more often. If it gets too high you start swapping which is really bad.

Re: A new speed milestone for Chrome

#132
post #114

Earlier quoted context omitted.

Having an account banned and not being able to restore it or having to watch countless of ads slowing down my computer or not searching what I am looking for because of new ranking algorithms seems worse that a little bit of loading time :)

Use adblockers, Use different search engine if you don't like it. Can't comment about account being banned.

> Use adblockers

To be fair, this is the same company pushing Manifest V3, which might kill adblocking as we know it

Re: A new speed milestone for Chrome

#133

Does anyone else find that they can't ever tell a difference in browser speed in day to day use? I switched to FireFox for my personal use a few years before the "Quanutm" update when it was theoretically much worse than Chrome and didn't notice a difference. For the last few years, I've been using Chrome and FireFox side by side with Chrome for work and FireFox for my own stuff and switching back and forth feels pre…

Chrome feels a little faster to me, but I stick with Firefox because it doesn’t give me the same creepy big brother feeling as chrome and I can spare a few milliseconds per page load.

Come to think of it, I primarily use chrome to double check UI changes on a page served from my local computer. That’s probably the main reason it feels faster.

Re: A new speed milestone for Chrome

#134

I think that browser developers are optimizing the wrong thing. Specifically: they optimize for execution speed while they better optimize for minimum memory usage instead. Let me explain why this is more important. Let's say I am visiting a properly made website and it takes 10% of CPU to render. Even if browser devs make their browser twice faster, it will only save 5% of CPU time - and that would be completely unn…

Man, that math did not make any sense at all. A program can't use 10% of the CPU. It either uses the CPU or it doesn't. If a page renders with "5% CPU" measured over some interval that means it rendered twice as quickly, which is a substantial improvement.

Re: A new speed milestone for Chrome

#136
post #123
post #118

Earlier quoted context omitted.

How do you know that isn't just measuring that most people keep to 5 tabs because otherwise everything grind to a halt. That's about how many tabs my wife's old Chromebook can handle before she has to start closing old tabs.

I am assuming it grind to a halt because it is CPU bound and not Memory bound? In that case the premises of CPU optimisations are not important would be, inaccurate? In reality it is complicated when we have extra CPU cycle to burn developers tends to put fancy new things. Which is basically what andy giveth bill taketh away.

Probably "everything stops" because tabs consume too much memory and OS starts swapping data to disk.

Re: A new speed milestone for Chrome

#138

Earlier quoted context omitted.

I disagree. Memory is cheap. Battery life isn't.

DDR5 prices would disagree with you. Plus, most laptop manufacturers rip you off for every RAM spec bump. $400 - $500 to go from 16GB to 32GB?! They can f--k right off! Not everyone is making six figure SV salaries to not flinch at these prices. That's why I love the framework laptop.

[deleted]

Re: A new speed milestone for Chrome

#139

I have a friend who says: "when you invent more efficient lightbulbs, people do not consume less energy, they just get more light" Every time we did a milestone performance improvement in our infrastructure, e.g. search used to take few seconds, we reduced it to few milliseconds. One year later our colleagues were doing machinegun-like queries and the search was back to take 1 second, and it is just a matter of time…

Relevantly, here's the HTTP Archive's chart of page weights over time: https://httparchive.org/reports/page-weight#bytesTotal

The median is around 2MB, up from 1.5MB 5 years ago.

Re: A new speed milestone for Chrome

#140

I have a friend who says: "when you invent more efficient lightbulbs, people do not consume less energy, they just get more light" Every time we did a milestone performance improvement in our infrastructure, e.g. search used to take few seconds, we reduced it to few milliseconds. One year later our colleagues were doing machinegun-like queries and the search was back to take 1 second, and it is just a matter of time…

https://en.m.wikipedia.org/wiki/Jevons_paradox
Post reply on HN