Slashdot Mirror
Chrome Now Reloads Pages 28% Faster (techcrunch.com)
Google has announced that it has worked with Facebook and Mozilla to make page reloads in Chrome for desktop and mobile significantly faster. According to Google's data, reloading sites with the latest version of Chrome should now be about 28 percent faster. From a report: Typically, when you reload a page, the browser ends up making hundreds of network requests just to see if the images and other resources it cached the first time you went to a site are still valid. As Google engineer Takashi Toyoshima notes in today's announcement, users typically reload pages because they either look broken or because the content looks like it should have been updated (think old-school live blogs). He argues that when browser developers first added this feature, it was mostly because broken pages were common. Today, users mostly reload pages because the content of a site seems stale.
I reload pages because they are broken, generally due to an excess of advertising. Yes, I could filter out advertising but, I often get paid for having it there. Not that I look at it.
Chrome now reloads Facebook pages up to 28% faster. The rest of the web won't see the benefit.
Hm perhaps we could use similar techniques to avoid making those hundreds of network connections in the first place...
I reload pages for a variety of reasons depending on what I am doing. I already have to drop into dev tools and chose from a variety of reload "flavors" to get some tasks done. If they must persist in deciding for me what I really want to do based on what other people "typically" want to do, at least make the option to express my actual goal more easy to access.
Or, you know, GTFO with your over-engineered "solutions".
Because it'd be awful if the summary actually summarized what was being done. From the article:
To overcome this issue, the team simplified Chrome’s reload behavior and it now only validates the main resource. Facebook, just like other pages, says its pages now reload 28 percent faster, too, so the next time you want to check if your friends finally posted new pictures of their cute corgis to Facebook (and you are using the web app instead of the native FB app), you’ll now get the answer faster.
One liner description of the change...
They made refresh 28% faster by having it no longer refresh.
Guess it makes Ctrl-F5 even more useful...
I'm hoping this article is either wrong or incomplete. Otherwise, won't this mean a significant increase in breakages? Suppose the main resource relies on two resources, one of which is in the cache, the other of which isn't. Those two resources implicitly depend on one another in some way (e.g. a new version of JavaScript code might require a new version of CSS, or else rendering would be wrong and vice-versa). If the browser validates only the main resource, then unless the URLs for the resources changed, there's now a mismatch. Worse, there's no way for the user to fix it, because reloading doesn't revalidate any of the other resources.
It seems like revalidation of all subresources should happen if any of the following are true:
Then again, I've had so much trouble with CloudFlare caching that I've started putting version numbers in every JS and CSS filename, and I use a server-side include to let me bump that version number site-wide every time I touch something in a backwards-incompatible way, so if other folks use the same approach, then maybe this doesn't matter?
Check out my sci-fi/humor trilogy at PatriotsBooks.
From what I understand, this changes reload behavior so that reload doesn't completely reload a page. Won't this break the reload behavior when testing a page you're developing and/or when browsing pages that glitched temporarily? Would we end up with a "hold shift during reload" that all tech people will use instead?
Avantgarde Hebrew science fiction
Will the advertisers on the page see the additional hit?
First a scheduler and now caching. What OS feature should come next?
So Mozilla helped Google make Chrome faster? It's not clear what Mozilla's role and benefit in all of this...
I can confirm that doing nothing at all on a Facebook page takes 72% of your time.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Engineer A: Lets re-interpret intent to make it faster
Engineer B: Lets re-interpret intent to make it current
GOTO A
The history of HTTP cache headers are filled with this same contention between different people trying to reinterpret the meaning of words to further their narrow agendas.
This crap always ends with everyone having a headache without solving anything.
If you want to make reload better try adding mechanisms to explicitly signal intent so it can explicitly be acted on rather than hacking shit to make it work better for *you* because you can.
Web 2.0 stuff only works if you have a reliable low-latency high-bandwidth internet connection.
Funny that they designed this shit for mobile...
Add the ability to put an ETag in the HTML document along side the resources, so the browser doesn't have to make a conditional "if-none-match" request to check if it is stale.
<img href="blah" etag="12345" />
I feel like I read a book and somebody ripped out the last several chapters.
Don't feel too bad. You won't find those in the article either. Here's the only sentence you missed:
The team simplified Chrome’s reload behavior and it now only validates the main resource.
IE. it used to reload 100's of page elements (eg. checking the etag of each), and now it only checks the main page.
I occasionally find I need to do a SHIFT+Reload (or CTRL+SHIFT+R) to force reload of all elements. With this new "only reload main resource" feature, I sure hope they add a something similar to reproduce the old behavior because a full reload is MUCH more overhead than the current reloads, or provide an option to use the old behavior (hahaha, yeah right! modern app *adding* a setting/option!).
Great now I get to the 6 minute long "Waiting for cache" message 28% faster!
Can you read 28% faster??
I'm not a Facebook member. I never will be. Yet when I load pages from almost anywhere on the web I can detect background traffic to Facebook (unless I explicitly block traffic to Facebook in my HOSTS file). Facebook has absolutely no right to know what I'm doing on sites as diverse as my local TV station, Slashdot and Linux support sites, yet that traffic is considerable and can't help but affect my Internet performance. I bet they could have made Chrome work even faster if they blocked traffic to Facebook completely or at least gave users the option to not send information to Facebook.
I'm an American. I love this country and the freedoms that we used to have.
https://support.microsoft.com/...
Out of memory problems are because Microsoft is stupid. I don't know what Microsoft should really be doing but using the information at that link helped lots.
Cease and desist these criminal activities, APK. You already know you are in violation of the Computer Fraud and Abuse Act and your persistence in this is involving us in your criminal acitivies along with damaging Slashdot as they constantly make the lameness filter more overbearing to deal with your posts.
Change is certain; progress is not obligatory.
Cease and desist these criminal activities, APK. You already know you are in violation of the Computer Fraud and Abuse Act and your persistence in this is involving us in your criminal acitivies along with damaging Slashdot as they constantly make the lameness filter more overbearing to deal with your spam.
Change is certain; progress is not obligatory.
My God, I cannot wait until the day we all read on Slashdot (no doubt, it will be posted on the front page, I assure you!)
"Alex, the one known as the "Super Fag" APK, has been found dead today in his home from an apparent intestines puncture. It would seem Mr APK was forcing what is known as a 'fake horse cock' up his rectum, which resulted in his colon and intestines being perforated and, ultimately, causing him to bleed out. He shall be missed greatly in this world as is known as "THE BEST SOFTWARE WRITER EVER" due to his AMAZING invention KNOWN AS THE HOST FILE. Who will ever take up his mantle now?
More on this horrific story at 11!"
I'll have you all now though, be careful using his "WaReZ" that he's pushing. Be sure to step through some IDA or something else, first. You'll be shocked when you find out what his software is doing behind the scene. Talk about 'soul'd out! (as he says)'
I don't care what malwarebytes said or some retarded online virus scanner. I've seen your code and I've seen what you're doing. You may want to come clean, or I'll start releasing it.
And I'm not trolling you. I also have quite a nice life, Thank you very much. I, unlike you, don't have to spam Slashdot all day like you to feel 'wanted' (Hint: No one likes you.)
You put people down when you start to feel inadequate. Your mental illness is so blatantly obvious that it hurts. Why don't you try posting as a real account for once, loser. Or did mommy not breastfeed you enough?
P.s. Fake name? Says the little fat retard hiding behind the AC name.
Pitiful attempt, Alex.
My name is Mike. I have no need to hide my name. I actually have a set of balls that work, unlike you.
so they have been doing a shift-refresh for every refresh?
Snowden and Manning are heroes.
The original article quotes a facebook article, which speaks about reducing requests by using cache with long expire headers.
Their approach: expire header for one year, filename with a content hash.
This means, facebook spams your browser cache with data, which will never be accessed again after they changed it, just to reduce the number of "if-modified" requests.