4 ms·
These 20 async calls don't actually need to reestablish the connection nowadays, so you don't actually get a significant performance penalty anymore for doing m
by y4mi 5y ago
These 20 async calls don't actually need to reestablish the connection nowadays, so you don't actually get a significant performance penalty anymore for doing multiple requests.
Unless the requests are triggered after another request finished of course. That's still significantly impacting loading times
- hamburglar 5y agoNot having to reestablish the connection is a nice thing, but 20 round trips is still 20 round trips. Lots of opportunity for delay there.
- giantrobot 5y agoYeah this is something people love to gloss over. On good 5G the connection latency might be 15-20ms to some topographically "close" server. Realistically that's an absolute minimum and you'll see 50-100ms latency to actual servers. When work depends on those resources it can't even start until all the data is returned. Far too often nothing can happen until a case are of resources gets returned. Then there's the fun outlier of some slow AdTech script that finally returns, screws with the DOM, and causes a layout and repaint. It's just today's "What Andy Giveth, Bill Taketh". Great job all around everyone.
- jcelerier 5y ago> These 20 async calls don't actually need to reestablish the connection nowadays, so you don't actually get a significant performance penalty anymore for doing multiple requests. why is everything so terrible to use then :-(
- csande17 5y agoBecause in practice, the 20 async calls are never actually made in parallel. The site makes one call, waits for it to finish, downloads a few more scripts, makes another call, parses the results of that call using an accidentally-quadratic-time algorithm, sends a bunch of tracking events over WebSockets and waits for them to finish, makes another call, uses that call to trigger a full-page React/Redux re-render, schedules another call in an asynchronous render effect handler...
- nexuist 5y agoAds, ads, and more ads. The Internet with an ad blocker vs. without is like a completely different universe. Most sites load pretty quickly with ads blocked, even complicated over-engineered SPAs.
- reaperducer 5y agoI've had to dial-back my ad blocker over the last six months or so. More and more web sites stall, or refuse to load at all with ad blockers enabled. Even ad-free ones like government web sites, because they use the same tracking mechanisms.
- dspillett 5y agoThat is just terrible design. A third party shouldn't be able to block first party functions like that. Though you are right, it does happen. If Google's tracking code doesn't load you can't buy tickets on Northern Rail's¹ site for instance. [1] Northern is one if the franchises running bits of the UK's "imaginatively" arranged railway system
- forgetfulness 5y agoI used to run without an ad blocker to support the websites I visited, but then too many would rev up my CPU and freeze my browser just because of all the ads they loaded. The experience of clicking a link started to become unbearable, and I went back to blocking ads. I know that circa 2018 the ad industry suffered a shock as major players started measuring more precisely what value ads brought, and CPC went down, I think things just got worse at this point because websites crammed more ads in response.
- chalupa-man 5y agoReddit and Medium are awful for this. I don't know what they're doing, but every page has a small chance of infinitely looping to max out a CPU core forever, unless you block their ads. I'll feel my laptop heating up and know that some Reddit thread somewhere is to blame.
- 5y ago