On Tue, Nov 29, 2016 at 10:27 PM, Levi Corcoran wrote:
> Thanks much. Memory allocation does indeed appear 'spread out' as a result
> of some recursive function calls of varying depth that get called during
> serialization, and a variety of code paths that can trigger the
> serialization, at leas
Thanks much. Memory allocation does indeed appear 'spread out' as a result
of some recursive function calls of varying depth that get called during
serialization, and a variety of code paths that can trigger the
serialization, at least after a quick skim through portions of very large
/debug/p
On Tue, Nov 29, 2016 at 6:57 PM, Levi Corcoran wrote:
>
> 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
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 applicat
