How Dgraph was running out of memory for some users, and how Go’s Garbage collector wasn’t enough, and Dgraph team used jemalloc to manage memory manually, which is a kind of hack.
I have read a ton about the strengths of Go’s garbage collector and how it’s getting better with time. Including the post, Getting to Go: The Journey of Go’s Garbage Collector from the Go blog.
Does the above post mean Go’s garbage collector isn’t as strong as they say?
1 Like
bot
5 November 2020 15:48
#2
Corresponding tweet for this thread:
Share link for this tweet.
1 Like
AstonJ
7 November 2020 16:37
#3
The article that just got posted here mentions memory management in Go DG, think you might find it interesting:
Is Zig the Long Awaited C Replacement.
Comparison with previous C contenders such as C++, D, Java, C#, Go, Rust and Swift
This thread was posted by one of our members via one of our automated news source trackers.
