2 ms·
The "slow" here is very relative. Yes, you can't push Discord -levels of messages with a GC language (like their famous "we moved from Go to Rust" post told us
by theshrike79 4y ago
The "slow" here is very relative.
Yes, you can't push Discord -levels of messages with a GC language (like their famous "we moved from Go to Rust" post told us all).
But you're not going to be at those levels any time soon, GC pauses are just fine in a good 99.99% of cases.
This kind of thinking is a type of premature optimization, you skip whole categories of technology (garbage collection) because you "feel" it's slow based on what you read about an edge case. =)
- lokedhs 4y agoExcept whatsapp at least used to run on Erlang, which definitely was pushing that kind of data. GC languages can have much better performance than non-GC languages (for many reasons, several of them mentioned here), and the main disadvantage being unpredictability. However, the unpredictability is not going to be problem for a chat application.
- keyczar931 4y ago99.9% of those posts from startup engineers saying "we migrated from X to Y" is because they wanted to play with technology Y and rationalised their decision.
- SirGiggles 4y ago> Yes, you can't push Discord -levels of messages with a GC language (like their famous "we moved from Go to Rust" post told us all). You can to a (pretty big) degree, as Discord have publicly stated in engineering blog posts: - https://discord.com/blog/how-discord-scaled-elixir-to-5-000-000-concurrent-users https://discord.com/blog/how-discord-scaled-elixir-to-5-000-... - https://discord.com/blog/using-rust-to-scale-elixir-for-11-million-concurrent-users https://discord.com/blog/using-rust-to-scale-elixir-for-11-m...
- winrid 4y agoIIRC they fixed a worst case latency of like 300ms in their LRU cache. These were periodic spikes. I doubt users really noticed a change from this. Maybe, it saved them some money...