News for hackers. Stuff that matters.
Re:Go hits the concurrency nail on the head by marcosdumay on Thursday October 04, 2018 @08:43PM (#18144830)
If they exist, they are running software written on either C or Rust, that can avoid memory efficiency traps and can schedule their workers on a more optimum way than a general purpose language.

That said, I'm not sure such thing exists. Just the memory overhead some common libraries impose on connections is enough to fill some 32GB.

Re:Go hits the concurrency nail on the head by toast0 on Thursday October 04, 2018 @10:50PM (#18145382)
Erlang works just fine for that many connections (depending on how much CPU you spend doing real work per connection). Socket buffers are tunable. 32GB isn't that much ram for a server, Android phones are shipping with 6gb, you can get 6TB into a server without getting too exotic.
Re:Go hits the concurrency nail on the head by dboreham on Friday October 05, 2018 @12:35PM (#18149517)
>That said, I'm not sure such thing exists.

Just to clarify : my knowledge on this is pretty deep so the only reason I didn't say "they exist" is that I don't personally have one in my DC (I've only managed up to 200k live connections). I know people very well who do. But yes of course the application would be written in some efficient language fit for the purpose like C, Rust, Go, Erlang. Probably not Java.

Also 32GB is not much memory these days.

Re:Go hits the concurrency nail on the head by NightlyDev on Thursday October 04, 2018 @11:17PM (#18145473)
3 million connections: https://medium.freecodecamp.org/million-websockets-and-go-cc...

Heck, you can probably handle a million connections using PHP(with swoole).

Re:Go hits the concurrency nail on the head by zzzcpan on Friday October 05, 2018 @08:29AM (#18147551)
In the article they got rid of goroutines to get to 3 million connections.