4 ms·
definitely not relevant to all web-dev, but Discord found that the garbage collection in go was causing bad performance spikes and switched to go for one of the
by pflock 6y ago
definitely not relevant to all web-dev, but Discord found that the garbage collection in go was causing bad performance spikes and switched to go for one of their read-state services: https://blog.discord.com/why-discord-is-switching-from-go-to-rust-a190bbca2b1f?gi=23a295f6604b https://blog.discord.com/why-discord-is-switching-from-go-to...
- ZeroCool2u 6y agoThis is such a great article. It's one of the examples that comes to mind when people ask me about great engineering blog posts. The TL;DR is the Go GC was causing some fairly large latency spikes under load. Since Rust doesn't do GC, because of its ownership model, these latency spikes didn't exist in their Rust implementation of the service. Also, pflock you have a small typo there. You probably meant to say from Go to Rust, not Go to Go :)
- burnthrow 6y agoKeep in mind this post is lolspeed porn, not a compelling argument against using a GC in your new project. If you're successful enough to have these problems, you can afford to rewrite in anything.