4 ms·
The GC cycles were triggered not due to heap size but due to the forced 2 minute max time between GC cycles [0], so a ballast wouldn't have helped here. [0]: h
by aw1621107 6y ago
The GC cycles were triggered not due to heap size but due to the forced 2 minute max time between GC cycles [0], so a ballast wouldn't have helped here.
[0]: https://github.com/golang/go/blob/0f66fb7b856b02497cf801ce72d80f375f53358b/src/runtime/proc.go#L5015 https://github.com/golang/go/blob/0f66fb7b856b02497cf801ce72...
- ttymck 6y agoThis is really interesting. Are there not alternative runtimes, or configurable gc periods? My understanding of the JVM GC is limited, but it seems highly configurable: does it (or other languages/VMs) have an analogous construct, and is it (usually) configurable?
- masklinn 6y agoThe Go core team intensely dislikes tunables, so Go has very few of these (really the opposite of the JVM). There is a central issue for GC tunables, but it's mostly where the various concern GC have gone to die so far: https://github.com/golang/go/issues/42430 https://github.com/golang/go/issues/42430