While investigating climbing memory usage for one of our services, I've
noticed a continual increase in the BuckHashSys metric from
runtime.MemStats ("bytes of memory in profiling bucket hash tables"), from
0 to ~2.5GB in the span of about 20 days, and no signs of stopping. This
is an application with a fairly steady ~8GB HeapInUse.
I've checked and we're using the default MemProfileRate granularity. We do
regularly call runtime.ReadMemStats() (every 30 seconds) for logging
purposes, and we do have the pprof endpoints wired up for debugging as
needed, although we shouldn't have anything regularly capturing profile
data AFAIK.
This is currently on Go 1.5.3 for various reasons, although I believe
they're upgrading to 1.7x with their next deployment and I'm eager to see
how things behave there.
What factors could be contributing to that continual climb of BuckHashSys
and how can we control/mitigate that?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
