Interesting tidbit from https://medium.com/@val_deleplace/go-code-refactoring-the-23x-performance-hunt-156746b522f7 … — “The execution time is now dominated by the allocation and the garbage collection of small objects (e.g. the Message struct), which make sense because memory management operations are known to be relatively slow.”
-
Show this thread
-
This is why you use a generational garbage collector with bump allocation in the nursery!
3 replies 2 retweets 20 likesShow this thread -
Replying to @pcwalton
Wait, Go *doesn't*? I feel like the more I learn about Go the more confused I get about why it's meant to be so great.
2 replies 0 retweets 3 likes -
Replying to @gsnedders
No, Go doesn’t. The language designers have for some reason decided they don’t want generational GC, and defend this choice. :(
2 replies 0 retweets 4 likes -
Replying to @pcwalton @gsnedders1 reply 0 retweets 1 like
Replying to @reusee @gsnedders
Told you Go needed generational GC. ;)
8:02 AM - 26 Sep 2018
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.