With help from Nelson Mimura Gonzalez and Bryan S Rosenburg I was able to
make some progress on the relationship between the cgroups view and the
procfs view.
In the cgroups view: `memory.usage_in_bytes` is the sum of
`memory.stat:rss` + `memory.stat:cache` + `memory.stat:mapped_file` +
> Subject: [EXTERNAL] [go-nuts] Re: basics of understanding golang memory
usage
> Sent by: golang-nuts@googlegroups.com
>
> I collected data on an example program from four angles. See
> https://docs.google.com/document/d/
> 1KUz7IjnD93X2VTVkRAhhNa7rHScCaIH8GLrsoaDIW_g for
I collected data on an example program from four angles. See
https://docs.google.com/document/d/1KUz7IjnD93X2VTVkRAhhNa7rHScCaIH8GLrsoaDIW_g
for the raw data and my puny attempts to correlate the four views. There
are some exact equalities, some near matches, some gross differences in
things
FYI, after asking on Slack I got some useful pointers:
- https://golang.org/pkg/runtime/#MemStats - definitions of memory stats
from the golang runtime
-
https://github.com/prometheus/client_golang/blob/master/prometheus/go_collector.go
- the code that publishes golang runtime memory stats as
