8 ms·
I don't know enough about rust to confirm or deny that -- but unless rust somehow puts a limit on in-flight async operations, I don't see how it would help. Th
by floating-io 5mo ago
I don't know enough about rust to confirm or deny that -- but unless rust somehow puts a limit on in-flight async operations, I don't see how it would help.
The problem is not resource usage in go. The problem is that they created umpteen thousand TCP connections, which is going to kill things regardless of the language.
- verdverm 5mo agocase in point, an old HN post about scaling Go to 1M websocket connections https://news.ycombinator.com/item?id=21865715 https://news.ycombinator.com/item?id=21865715
- slopinthebag 5mo agoGo can scale but only if you sidestep goroutines and use something like https://github.com/lesismal/nbio https://github.com/lesismal/nbio (which is awesome, highly endorse)