unless the data is changing on every request, that sounds like a caching problem, but that's a bit beyond the scope of a twitter thread. there's like a 90% chance the answer is to cache something in redis. DMs are open if this is actually something you want help with.
-
-
This Tweet is unavailable.
-
my dude you can put all these things on the same machine if you want. The problem is that disks are slow, and the solution is to cache things in memory. That's literally all it is.
1 reply 0 retweets 1 like -
I would love it if it were the case that the primary problem with website speed was data coherency. It isn't. You can trivially hit F12 on most large commercial websites, do a perf and network trace, and see exactly what the problem is: craptons of serially dependent JS libs.
1 reply 0 retweets 10 likes -
Replying to @cmuratori @jordanorelli and
To make matters worse, a lot of times these JS libs _aren't even hash named_, so they have caching effectively turned off, which makes them load everytime. And of course, don't get me started on the craptons of advertising tracking crap that each take ~20ms. It's horrible.
1 reply 0 retweets 9 likes -
Replying to @cmuratori @jordanorelli and
I wasn't really joking with my original post. Web developers hand wave at a lot of actually hard problems ("it's network latency! it's data coherency! it's scalability") but if you actually profile the sites, none of those things are actually the problem.
2 replies 0 retweets 10 likes -
that's casting a huge net. A lot of web developers would agree that the web sucks and most websites suck. Any web developer that enjoys web development isn't worth hiring. Most decent web developers are web developers for exactly one reason: it's the only job they can get.
1 reply 0 retweets 1 like -
Replying to @jordanorelli @cmuratori and
I know how smart you are, I watch handmade hero, but for real, experienced developers in one domain shitting on inexperienced developers in another domain is destructive to the craft.
2 replies 0 retweets 2 likes -
Inexperienced? We're talking about sites run by companies with billions of dollars who have had literal decades to write their sites. I am shitting on very "experienced" developers, for whatever definition we want to give that term?
1 reply 0 retweets 2 likes -
"Oooh look! Someone released a new JavaScript framework!" ^ that's making fun of inexperienced web developers, and has absolutely nothing to do with Amazon going down on Prime Day. site reliability engineers on sites like Amazon are very far from the client-side JS code.
1 reply 0 retweets 1 like
I guess the joke was too complicated? The joke was that it's the JavaScript frameworks that make the site slow, not the back end, even though people always claim back end issues are what makes the web slow. Also, no, experienced web devs all seem to use frameworks!
-
-
Replying to @cmuratori @jordanorelli and
I mean at least if you just look at http://youtube.com , http://facebook.com , https://twitter.com , etc., etc., there is tons of OSS JavaScript getting pulled in there. This is not some "my first web site" thing.
1 reply 0 retweets 3 likes -
I haven't worked on those feeds, so I can only guess as to why, but I spent like six months working on Etsy's feed a few years ago. # of requests is a poor metric; the metrics that are noticeable to users are things like time to first byte and time to first paint.
1 reply 0 retweets 0 likes - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.