Import Semi-Automated GOGC Tuning To Avoid GC Frequently

[hawkingrei]

Enhancement

Extensive experiments are needed to verify its feasibility.

Introduction

Inspired
by How We Saved 70K Cores Across 30 Mission-Critical Services (Large-Scale, Semi-Automated Go GC Tuning @Uber)
.

 _______________  => limit: host/cgroup memory hard limit
|               |
|---------------| => gc_trigger: heap_live + heap_live * GCPercent / 100
|               |
|---------------|
|   heap_live   |
|_______________|

For Golang 1.18

In Golang1.18, The garbage collector now includes non-heap sources of garbage collector work (e.g., stack scanning) when determining how frequently to run. As a result, garbage collector overhead is more predictable when these sources are significant. For most applications these changes will be negligible; however, some Go applications may now use less memory and spend more time on garbage collection, or vice versa, than before. The intended workaround is to tweak GOGC where necessary. Semi-Automated Go GC Tuning is more important than ever.