Am I so wrong to stop reading after a grammatical error on the very first word in the article? https://www.google.com/search?q=everyday+two+words+or+one
You couldn't be wronger.
A new speed milestone for Chrome
81–90 of 161 posts
Re: A new speed milestone for Chrome
#82I 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…
... and some of us disable swap to prolong laptop-motherboard-soldered-SSD lifetime, and Windows 10 regularly bluescreens when memory is exhausted and swap is disabled.
Re: A new speed milestone for Chrome
#83I 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…
> You might ask, what about modern websites, built with D*t compiled to webassembly, GPU acceleration, reactive frameworks, material design and capable to load the multi-core CPU at 100%? I am not using such sites so I don't care.
Does this just mean that browser developers are optimizing for the right thing, just not something that benefits you? Tons of people use these sites.
> If the system starts swapping, it becomes orders of magnitude slower.
Not really. Browsers try to keep stuff in swap that they probably won't need. Swapping doesn't become a problem until you're almost out of memory as well, and then you might get thrashing. But there's a wide range where CPU optimizations make sense. And such a large fraction of people have SSDs that even swap access can be pretty fast.
Re: A new speed milestone for Chrome
#84I 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…
I disagree. Memory is cheap. Battery life isn't.
Re: A new speed milestone for Chrome
#85I 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…
I disagree. Memory is cheap. Battery life isn't.
High memory consumption eats battery life too
Re: A new speed milestone for Chrome
#86"Nothing is more frustrating than having a slow experience while browsing the web"
^ I stopped reading at this point, because I realised that this is something that only someone on a marketing team would write. A perfect combination of incorrect and disingenuous.
Re: A new speed milestone for Chrome
#87Earlier quoted context omitted.
https://jsbench.github.io/#b39045cacae8d8c4a3ec044e538533dc Look at DOM performance. Chrome has a ceiling of about 45m ops/s where FF max speed is dependent upon your ram and bus speed reaching beyond 4-5b ops/s. In both though querySelectors perform at about the same speeds as slow as 25000 ops/s. I have written an OS GUI that executes in the browser. It loads, including full state restoration in about 120ms. I was…
I suspect that isn't why you weren't hired.
Why would you suspect that? Are you a JavaScript developer? If so have you seen the terrifying horror on people’s faces when you mention alternatives to querySelectors or that you can write/execute code faster by not using vDOM? Mentioning performance is the fastest way to exit a job interview.
Re: A new speed milestone for Chrome
#88I 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…
> Optimizing for speed usually causes increased memory consumption, Lol, no? If your benchmark is memory bound, reducing memory usage is probably the simplest way to make it faster.
He is right though. Chrome isn't memory bound... yet.
Re: A new speed milestone for Chrome
#89I 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…
> Optimizing for speed usually causes increased memory consumption, Lol, no? If your benchmark is memory bound, reducing memory usage is probably the simplest way to make it faster.
There are some truly memory-bound problems, but I believe the parent comment is correct on average. A lot of common speed issues can be helped by: adding a cache, adding an extra lookup index, memoising calculated values, adding a new denormalised data projection, etc. I think "usually" was a fair description.
Re: A new speed milestone for Chrome
#90"Nothing is more frustrating than having a slow experience while browsing the web" ^ I stopped reading at this point, because I realised that this is something that only someone on a marketing team would write. A perfect combination of incorrect and disingenuous.
Why? I find slow and janky websites insufferable.