When running on baremetal, however, we found two key limitations of the Go runtime so far: Systems with a lot of RAM can have a lot of allocations, prompting the Go Garbage Collector to aggressively steal CPU. 2. Applications performing hundreds of thousands of requests per second may make use of thousands of TCP sockets, bottlenecking the Go runtime’s network backend on syscalls.
Split from #31908 (comment) and full write-up at https://jazco.dev/2024/01/10/golang-and-epoll/. tl;dr is that a program on a 192 core machine with >2500 sockets and with >1k becoming ready at once...
I come across a lot of blog posts about the AT Protocol and Bluesky technicals – both on Bluesky official blogs and those of the team members, and by independent developers from the community. So many people are blogging now (especially now that Leaflet got popular in these circles) that I started using an RSS reader again just to keep up with everything.