Should't we stop sending 100 IP packets on every keystroketo start with?
I could be misunderstanding, but typing "l" into the terminal should send one byte, which should fit into one TCP packet
Nobody likes lag: How to make low-latency dev sandboxes
31–40 of 47 posts
Re: Nobody likes lag: How to make low-latency dev sandboxes
#32When Covid hit I wasn’t the only one working remotely at my company, but I was the only one working remotely in North America, and apparently the only one trying to Work Smarter. By then there were a handful of feature toggles I had implemented that I quickly set to always on in development, but chief among them was that gzip service calls were a net loss in AWS but very very handy while working from home. I also had…
One of the most dangerous ideologies is "all good things come to those who wait" or that waiting is a virtue. Applied by people working at all the levels of a system for years and years it leads to steps that could be 30ms taking 30s.
Another variant is that suffering is a virtue.
They say doctors make the worst patients. I wonder if programmers are the least useful of users.
Re: Nobody likes lag: How to make low-latency dev sandboxes
#33Should't we stop sending 100 IP packets on every keystroketo start with?
I could be misunderstanding, but typing "l" into the terminal should send one byte, which should fit into one TCP packet
It's a reference to https://news.ycombinator.com/item?id=46723990
Re: Nobody likes lag: How to make low-latency dev sandboxes
#34Earlier quoted context omitted.
I think sandboxes are having their moment because it's become undeniable that coding agents are useful, and that they're more useful if you run them in YOLO mode rather than having to approve everything they want to do. Coding agents are still a relatively new category to most people. Claude Code dates back to February last year, and it took a while for the general engineering public to understand why that format - c…
Why/how are they more useful in YOLO mode than in careful mode?
You can literally give them a task that will take a couple of hours to finish (like "port this library to language X, start by porting the tests, don't stop until all of the tests pass against the new implementation"), go out for lunch, come back and they'll have finished and probably got it ~90% right.
Re: Nobody likes lag: How to make low-latency dev sandboxes
#35Earlier quoted context omitted.
One of the most dangerous ideologies is "all good things come to those who wait" or that waiting is a virtue. Applied by people working at all the levels of a system for years and years it leads to steps that could be 30ms taking 30s.
Another variant is that suffering is a virtue. They say doctors make the worst patients. I wonder if programmers are the least useful of users.
My current ideology:
Wait on tasks that are urgent,
Act on ideas that are important.
Re: Nobody likes lag: How to make low-latency dev sandboxes
#36Interesting, I use cloudflare containers and it takes roughly 6-7 seconds to boot up using a very lightweight image.
Re: Nobody likes lag: How to make low-latency dev sandboxes
#37Thanks for sharing. Makes a lot of sense that removing that routing layer would improve e2e latency. We had a similar bottleneck building out our sandbox routing layer, where we were doing a lookup to a centralized db to route the query. We found that even with a fast KV store, that lookup still added too much overhead. We moved to encoding the routing logic (like region, cluster ID, etc) directly into the subdomain/…
Pingora looks good https://github.com/cloudflare/pingora
Re: Nobody likes lag: How to make low-latency dev sandboxes
#38> TL;DR: If you want low latency sandboxes, cut out the middlemen and put your servers next to your users.
Valuable insight /s
Re: Nobody likes lag: How to make low-latency dev sandboxes
#39If you don’t have control over all these pieces and just need terminal (ssh / remote vim etc), highly recommend https://mosh.org/
Re: Nobody likes lag: How to make low-latency dev sandboxes
#40This is a problem that doesn't need to exist. Just run stuff locally on your dev machine with 12 cores and 32Gi of memory. What the hell has happened to need an entire computing cluster and all the network infrastructure between just to write software?