I've measured resident size multiple times, with top, /proc/pid/smem, pmap.
There is a huge allocated region towards the end of virtual memory:
7fba77bb0000-7fbc3bf37000 rw-p 00000000 00:00 0
Size: 7409180 kB
Rss: 7408840 kB
Pss: 7408840 kB
Shared_Clean: 0 kB
Shared_Dirty: 0 kB
Private_Clean: 0 kB
Private_Dirty: 7408840 kB
Referenced: 7179916 kB
Anonymous: 7408840 kB
AnonHugePages: 243712 kB
I've tried to force GC through /pprof/debug/heap?gc=1, didn't have any
effect (gc was called, but nothing freed).
This doesn't fit to my understanding as well. If we don't use CGO all
memory should be reported somewhere?
On Wednesday, February 14, 2018 at 3:05:26 AM UTC-8, Peter Waller wrote:
> First, a sanity check: How are you measuring the resident set? Are you
> certain the memstats data you presented are from the same run (and after)
> you hit 10G resident?
> What you have described doesn't immediately fit in my mental model. Could
> you be measuring the VM size rather than the resident size? The thing that
> puzzles me a little is that your "Sys =" field is so much lower than 10G,
> assuming the measurements were taken at the same time.
> Have you tried calling runtime.FreeOSMemory and playing with GOGC
> (described in pkg/runtime <https://golang.org/pkg/runtime/> docs), do
> those make any difference? You might also want to play with
>> Both memory profile and heap debug show ~500MB memory is in use, idle
>> heap is pretty low, given all that and lack of cgo, where rest 10.5G could
>> go and what are tools to debug it?
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.