Sounds like Discord was running gigantic in memory Go caches.

Not that it's the wrong approach, but this is a very real-time system-y problem that Rust is designed for. So I understand why this made sense.

Obviously rewriting in Rust worked for them, but I'm curious if they tried the Ballast[0] approach, along with smaller cache's per service. That would make the GC scan on the cache smaller while still avoiding some of the Go startup heap issues. I'm not sure if the target heap size ever was accepted by the Go team, but it may have been easier than a full rewrite.

[0] https://blog.twitch.tv/en/2019/04/10/go-memory-ballast-how-i...