3 ms·
The author did say CPU efficiency is key, and Erlang isn't exactly known for its raw speed. In general search is very CPU intensive, maybe that's why Google ne
by continuations 13y ago
The author did say CPU efficiency is key, and Erlang isn't exactly known for its raw speed.
In general search is very CPU intensive, maybe that's why Google never adopted Erlang.
- banachtarski 13y agoYes but intentionally so. There is an intrinsic tension between latency and throughput. Erlang chooses willfully to optimize for the former rather than the latter. This works when the majority of the tasks occurring concurrently are typically small and lightweight (aka, a web server).