We recently received several customer reports regarding CRI-O memory usage, consumption and alleged leaks. While troubleshooting, we found that there are areas with CRI-O that could be responsible for the process memory consumption growing over time, especially its virtual address space usage that often confuses our customers. We could see whether there would be any feasible countermeasures that we could employ to help with the situation a little.

Thus, I would like to focus on the following area:

• Use the GOMEMLIMIT together with GOGC settings to tune Go's GC during runtime
  • How adjusting both settings would help (or not)
  • Can these be adjusted dynamically or during CRI-O startup?
  • Would using some "auto-tuner" package/solution benefit CRI-O?