4 ms·
If you have to handle that many connections, I would suggest looking at Erlang. Its default heap of a process is < 3K. Usually that shouldn't matter as much as
by rdtsc 13y ago
If you have to handle that many connections, I would suggest looking at Erlang. Its default heap of a process is < 3K.
Usually that shouldn't matter as much as both have small process sizes compared to OS threads or processes. But at millions of connections it starts to matter. Whatsapp for example, was running on FreeBSD and Erlang with 2M+ connections.
- ballard 13y agoGo needs optional arguments for goroutines and have global defaults because recompiling is ludicrous. Erlang is an ok language with a great runtime. Elixir is much higher level language and hence more productive for teams that already know Erlang but want to write less code and build faster. Also with Erlang, static type checking not used much in Erlang and big loss unless you use dialyzer. Advantage go for compiling and running test cases laser-blindingly fast. There is a native QuickCheck framework for Erlang, and I'm sure someone wrote a go one.
- enneff 13y agoHave you tried recompiling Go? This is building the tool chain and standard library on my modest machine with a cold cache: $ time ./make.bash real 0m42.763s user 1m11.655s sys 0m13.411s Hardly a colossal burden.
- ballard 13y agoI've run it a zillion times. That's not the point, and that doesn't solve the problem. The point is per goroutine configurable stack sizes.