> "The internet"
Classic software engineer perspective.
I have good friends who build their entire career between "ISP" and "Load Balancer"
200 Milliseconds
61–70 of 114 posts
Re: 200 Milliseconds
#62This is magnificent! Gave me roller-coaster ride across 40 years of gathering knowledge about computers and networks. I'm very jealous of whoever created that. Well done!
I once asked a question like this for an interview. "Tell me what happens when you press the Buy button on a web site". It really helped me gauge a sense for the person's interests and expertise. Like some folks just talked about javascript and some node code. Others talked about tcp a bit, some got into cloud stuff. It was really telling. Not bad or good, just a great way to learn where someone's head is at and was a fun back-and-forth conversation.
This web site is basically a cheat code for that question lol. So well done, kudos to the author. Bookmarked and shared
Re: 200 Milliseconds
#63This is magnificent! Gave me roller-coaster ride across 40 years of gathering knowledge about computers and networks. I'm very jealous of whoever created that. Well done!
You are not jealous. You are envious. Homer explains it best https://youtu.be/Tmx1jpqv3RA
Not really, jealous is defined as envious (being envious is one of the definitions of being jealous).
For common usage they are equivalent, e.g. I'm jealous of X is the same as I'm envious of X.
Re: 200 Milliseconds
#64[dead]
Re: 200 Milliseconds
#65Great read. I was already familiar with the overall concept, but the step-by-step, chronological explanation made it much easier to understand.
Highly recommended for infrastructure engineers, solution architects, and developers.
Re: 200 Milliseconds
#66Earlier quoted context omitted.
You are not jealous. You are envious. Homer explains it best https://youtu.be/Tmx1jpqv3RA
Not really, jealous is defined as envious (being envious is one of the definitions of being jealous). For common usage they are equivalent, e.g. I'm jealous of X is the same as I'm envious of X.
They may be equivalent in common parlance, but that’s a bit like saying it is ok to use ‘your’ instead of “you’re” just because it is so common.
We say “jealously guarded’ not ‘enviously guarded’ for a reason. Jealousy is about being protective of your own possessions and relationships; you feel jealousy if your spouse responds well to a coworker’s flirtations. Envy is when you find think of the coworker’s luck in having a good looking spouse
Re: 200 Milliseconds
#67Fine, but what is the journey of the p99.9 900ms request?
Re: 200 Milliseconds
#68is it bad that while this does look like a really cool method to explain a complex topic, my instinct on reading mic-droppy, RLHF AI prose is to be dismissive? there's just something about the persistent mic drops and this-not-that writing that feels so cheap I think it's because the explainer is passive, there's no interiority, it tells and doesn't show. plus, stylistically, if this were rewritten in second person (…
"mic-droppy" is the perfect description. Now I can imagine Claude sheepishly picking up the mic yet again after I correct it.
Re: 200 Milliseconds
#69>touchpad controller
>capacitance dip → interrupt raised
>hid driver report: x 512 · y 288 · button 1 down
>...
>One millisecond in, the click has passed through four pieces of software and nothing has left the laptop.
I'm going to press X to doubt.
There's no way you're getting from "finger touching glass" -> "chrome seeing a click" in one millisecond. Heck, I know for a fact that even the cap touch controller isn't going to be that quick.
I would believe it's closer to 40-50ms, E2E. Even if the captouch was instantaneous, 1ms latency latency is in the realm of RTOS, not a general-purpose OS feeding a bloated app like chrome.
Re: 200 Milliseconds
#70Am I crazy if for something like an online purchase, I kind of expect it to take a second or two to process the payment, so I would assume something went wrong if it was 200ms?
With the speed of modern internet connections, I'd honestly think something were wrong if it took a couple of seconds. I'd expect almost instantaneous results. What amazes me every time is the amount of things happening in that short amount of time though. The amount of endpoints/channels the signal has to go through to go from "I want to buy this" to "You bought it!".