Noticing when an app is only hosted in us-east-1

Post by XiS » Thu, Jun 29, 2023, 9:32 AM UTC

bob1029 wrote: post #69

cbzoiav wrote: post #45

Earlier quoted context omitted.

Size isn't even the worst of it. It's number of requests. You need to go through a TCP handshake for every connection you open. You can reuse the connection but that means queuing requests and hitting the latency as a multiplier. Browsers also have a cap on parallel connections so when you get enough requests it queues either way. HTTP/2 reduces the problem with multiplexing but it still doesn't go away. If your app…

> It's number of requests. Absolutely. This is the prime hallmark of shitty, slow web. If you fight your battles here everything else will fall into place. I've started building our B2B web apps where the server returns 1 final, static HTML document in response to every resource. There are no separate js/css resource URLs at all in our products anymore. Anything we need is interpolated into the final HTML document sc…

Post by parasti » Thu, Jun 29, 2023, 9:40 AM UTC

Dalewyn wrote: post #72

cbzoiav wrote: post #45

Earlier quoted context omitted.

Size isn't even the worst of it. It's number of requests. You need to go through a TCP handshake for every connection you open. You can reuse the connection but that means queuing requests and hitting the latency as a multiplier. Browsers also have a cap on parallel connections so when you get enough requests it queues either way. HTTP/2 reduces the problem with multiplexing but it still doesn't go away. If your app…

>If your app has to make 40 requests pulling in js files, CSS files fonts, API calls etc. to show something useful that will be visibly slow To put this in a way the common man can appreciate, imagine you're at a restaurant and you ordered some clam chowder and your waiter brings it to you. If the waiter brings you the chowder complete in one bowl, you get the chowder then and there. That is HN and most websites from…

Post by pcthrowaway » Thu, Jun 29, 2023, 9:53 AM UTC

hunter2_ wrote: post #61

jaggederest wrote: post #56

Earlier quoted context omitted.

Remember back in the old days when people used to concatenate images into imagemaps and specify the coordinates and dimensions? One image file for a whole site. Same goes back when we could just load a single library from the Google public version (cough-jquery-cough) and then all the on-page JS was just in-tag handlers. Not that it was better but boy howdy was it faster to load.

You're probably thinking of CSS sprites, if you mean only displaying a certain portion of the image file at a time. An image map is when you display the whole image file as-is, but have different clickable links at different coordinates/dimensions. The former is specifically for reducing requests, while the latter is more about UX.

Post by rozenmd » Thu, Jun 29, 2023, 10:03 AM UTC

eXpl0it3r wrote: post #106

rozenmd wrote: post #77

Earlier quoted context omitted.

Here, I built a tool to help you visualise what response times are like from around the world so that you "buy this" idea: https://onlineornot.com/do-i-need-a-cdn?url=https://news.yco...

Where are the request servers hosted? What's the peering like for those hosts? I feel like people also often forget that bad peering by ISP can have a big influence on the overall latency.

Post by hutzlibu » Thu, Jun 29, 2023, 10:09 AM UTC

noitpmeder wrote: post #78

nottorp wrote: post #71

Earlier quoted context omitted.

Q1: Why would round trip latency matter so much when the modern web 45.0 adds so much overhead? Q2: Why don't we just force all the SV techbros to test their sites - AND their browsers - on a $200 notebook with eMMC storage from 2 years ago?

Because most sites aren't interested in their users who use bad hardware as a market share. The most attractive client base are the ones with money to spend.