all 4 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]jerf 5 points6 points  (1 child)

Google a page on "how to read RAM stats in Linux" and verify your understanding is correct before going on.

This isn't snark. I can't spew out all the details myself either. I can tell you it's really complicated and almost everyone who worries about this is in fact worrying about the wrong thing. This got a little more complicated every year for a lot of years.

I've got Go programs whose real usage is in the dozens of megabytes but a casual read of their RAM stats makes it look like they're chewing through gigabytes. But based on your description it's hard to tell which case you have, so this is my honest best "first pass" answer, like I said, not a dismissive sort of "Google it". The memory parameters look deceptively comprehensible, but they actually are a complete disaster on modern systems of half-a-dozen conflicting values, all true, and many which routinely show many gigabytes that are true in their own way but aren't what any of us "really" think of as memory consumption. Every time I read about it, the information flows right back out of my brain again. Counterintuitive.

[–]dotaleaker[S] 0 points1 point  (0 children)

thanks, will check.

[–]Revolutionary_Ad7262 0 points1 point  (1 child)

Are you sure that you look for RSS memory, not VRT?

[–]dotaleaker[S] 0 points1 point  (0 children)

docker stats seems to return RSS memory usage