y that number was being read by automemlimit.
> (Or it could be some other package dependency adjusting these parameters at
> init time. Or it could be something changing your program's environment
> variables.)
>
> On Friday, January 17, 2025 at 8:44:58 AM UTC-5 Felix Böwing w
We recently had the problem, that the go garbage collector ran hot on a
kubernetes pod and we didn’t find out why. Specs were as follows:
- heap size as reported by the GC was roughly 3GB
- GOGC percentage was at 100
- GOMEMLIMIT was set to something way above current heap size (6750M
