On 4/27/18, Reco <recovery...@gmail.com> wrote: > Hi. > > On Fri, Apr 27, 2018 at 12:26:11PM +0000, Eduardo M KALINOWSKI wrote: >> On sex, 27 abr 2018, Simon Beirnaert wrote: >> > The bottom line for me is that I when I shut down everything I install >> > and manage on the system, it's still conuming about half a gig more >> > than a system running the exact same base image right after use, >> > without >> > the extra memory being accounted for by monitoring tools. >> >> How are you determining what you call "consumed memory"? > > OP's original e-mail mentioned free(1), vmstat(1) and smem(1). > All three lie :). > > >> Keep in mind that the kernel will by default use almost all free memory >> (not >> actually used by processes and libraries) as cache space, because it >> makes >> no sense to leave memory just laying around. However, once it's really >> needed, the caches will be dropped. Thus "free" memory is usually >> reported >> as low. Compare with "available" memory as reported by free.
Yeah, I took a shot at trying to help with this one, too, via searching apt for "monitor memory usage". Saw a couple possibilities, but so far nothing's reflecting what I know is going on. smemstat was the current standout. As normal user, it said my browser was using ~60MB or so. smemstate via root user shows closer to 1GB. That's a big difference... Meanwhile in reality and on a fresh reboot, "free -m" will lurch "used" from ~350MB to ~5 1/2 gigabytes as soon as all... open browser tabs.. are refreshed (offline). User experience of sporadic crashes lately backs that up as pretty much verified. Apparently ~600 tabs this morning. When a browser flashes that warning that opening more than a few tabs has potentially negative consequences.. they ain't just whistling Dixie... :) Cindy..... -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs... in search of more (very) cheap RAM *
