Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish MB
It would be a problem if I left it on this long regularly, and indeed it is a problem at the moment because I need to leave it on and at this rate I'll be using swap space to do actual work tomorrow just because it's powered on, which will be slow and wear out the SSD that my swap space has to

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Keith Edmunds
On Thu, 10 Sep 2020 22:01:20 +0100, hamis...@live.co.uk said: > but [...] using 20GB of RAM with almost nothing open [...] is not good > behaviour Why not? Is there an actual problem in the day to day use of the system? Or is the problem that you've seen some numbers you don't like the look of /

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 21:56, Keith Edmunds wrote: > Using swap is not a bad thing in itself (quite the opposite in many cases). > > The actual process of swapping is expensive, though, and you want to > minimise that. > > One way to see whether you have a lot of swapping going on is to run > "vmstat 1"

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Keith Edmunds
Using swap is not a bad thing in itself (quite the opposite in many cases). The actual process of swapping is expensive, though, and you want to minimise that. One way to see whether you have a lot of swapping going on is to run "vmstat 1" (you don't need to be root). That will produce a new

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 21:17, Keith Edmunds wrote: > On Thu, 10 Sep 2020 21:03:21 +0100, hamis...@live.co.uk said: > >> Any more ideas? This has definitely revealed something interesting, just >> not sure what it is yet/what to do about it. > > You don't need to do anything about it. Well, it keeps going

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Keith Edmunds
On Thu, 10 Sep 2020 21:03:21 +0100, hamis...@live.co.uk said: > Any more ideas? This has definitely revealed something interesting, just > not sure what it is yet/what to do about it. You don't need to do anything about it. -- Linux Tips:

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 15:44, Hamish McIntyre-Bhatty wrote: > On 10/09/2020 15:29, Ralph Corderoy wrote: >> ‘sudo slabtop -osc’ will give a breakdown. > Ignore previous message in moderation queue, using ix.io now. > > Okay, that yields: > > http://ix.io/2x4T > > The total is much smaller than the number

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 15:29, Ralph Corderoy wrote: > ‘sudo slabtop -osc’ will give a breakdown. Ignore previous message in moderation queue, using ix.io now. Okay, that yields: http://ix.io/2x4T The total is much smaller than the number in /proc/meminfo (just verified it hasn't changed drastically).

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Ralph Corderoy
Hi Hamish, > On desktop I seem to have a very high number for "SUnreclaim" in > /proc/meminfo: > > MemTotal:   32812004 kB > ... > Slab:   16832040 kB > SUnreclaim: 16434568 kB ‘sudo slabtop -osc’ will give a breakdown. -- Cheers, Ralph. -- Next meeting: Online, Jitsi,

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 15:07, Ralph Corderoy wrote: > Hi Hamish, > >> This is strange. If I close eg Firefox, the all the (20+!) listings >> for that process go away. > Did you have quite a lot of tabs in that Firefox? It uses multiple > processes these days, roughly number of tabs plus a few. Yeah, I

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Ralph Corderoy
Hi Hamish, > This is strange. If I close eg Firefox, the all the (20+!) listings > for that process go away. Did you have quite a lot of tabs in that Firefox? It uses multiple processes these days, roughly number of tabs plus a few. > What's weird is they all have PIDs, but there aren't that

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 14:17, Hamish McIntyre-Bhatty wrote: NB: On desktop I seem to have a very high number for "SUnreclaim" in /proc/meminfo: MemTotal:   32812004 kB MemFree: 8619976 kB MemAvailable:    9572924 kB Buffers:   61772 kB Cached:  1061212 kB SwapCached: 

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 14:12, Keith Edmunds wrote: > On Thu, 10 Sep 2020 14:07:00 +0100, hamis...@live.co.uk said: > >> No difference to the output. > Surprising. Here: > > $ ps aux|wc -l > 364 > $ ps maux|wc -l > 1872 That shows a difference similar to yours, but there is no difference in those use cases

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Keith Edmunds
On Thu, 10 Sep 2020 14:07:00 +0100, hamis...@live.co.uk said: > No difference to the output. Surprising. Here: $ ps aux|wc -l 364 $ ps maux|wc -l 1872 -- Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 14:03, Keith Edmunds wrote: > On Thu, 10 Sep 2020 13:57:09 +0100, hamis...@live.co.uk said: > >> ps aux > Doesn't show threads. Try "ps maux" (or, if you prefer, "ps -Lef"). No difference to the output. signature.asc Description: OpenPGP digital signature -- Next meeting:

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Keith Edmunds
On Thu, 10 Sep 2020 13:57:09 +0100, hamis...@live.co.uk said: > ps aux Doesn't show threads. Try "ps maux" (or, if you prefer, "ps -Lef"). -- Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ -- Next meeting: Online, Jitsi, Tuesday, 2020-10-06 20:00 Check to whom you

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 13:20, Keith Edmunds wrote: > On Thu, 10 Sep 2020 12:09:51 +0100, hamis...@live.co.uk said: > >> Using htop in that way seems to show processes that aren't currently >> running any more - like previous invocations of firefox, in the stats. >> Is that expected? > Not expected nor

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Keith Edmunds
On Thu, 10 Sep 2020 12:09:51 +0100, hamis...@live.co.uk said: > Using htop in that way seems to show processes that aren't currently > running any more - like previous invocations of firefox, in the stats. > Is that expected? Not expected nor correct. htop shows processes that exist in the

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 13:12, Terry Coles wrote: > On Thursday, 10 September 2020 12:59:49 BST Hamish McIntyre-Bhatty wrote: >> "free" should report physical "real" memory usage right? If I'm mistaken >> there it could explain the numbers. The NAS box had only 14M or 256M >> free earlier despite showing

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Terry Coles
On Thursday, 10 September 2020 12:59:49 BST Hamish McIntyre-Bhatty wrote: > "free" should report physical "real" memory usage right? If I'm mistaken > there it could explain the numbers. The NAS box had only 14M or 256M > free earlier despite showing no process using that much memory. It > usually

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 12:09, Hamish McIntyre-Bhatty wrote: > On 10/09/2020 12:03, Keith Edmunds wrote: >> What problem are you trying to solve? >> >> If you're just curious about memory usage, run htop, press F6 and sort by >> M_RESIDENT or, if you're feeling more adventurous, run atop and press M >> (not

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
On 10/09/2020 12:03, Keith Edmunds wrote: > What problem are you trying to solve? > > If you're just curious about memory usage, run htop, press F6 and sort by > M_RESIDENT or, if you're feeling more adventurous, run atop and press M > (not m). Either will show you how much memory each process is

Re: [Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Keith Edmunds
What problem are you trying to solve? If you're just curious about memory usage, run htop, press F6 and sort by M_RESIDENT or, if you're feeling more adventurous, run atop and press M (not m). Either will show you how much memory each process is using, with htop giving a less detailed but

[Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
Hi all, Sorry for spamming the list a bit lately! :) Another issue I've had on my desktop, is that after being powered on for after maybe 4 hours, my memory usage starts to climb, but no process is listed as having used much memory. After a few days, this is what "free -h" shows:  

[Dorset] Very high memory usage (ignoring cache) after being powered on for days

2020-09-10 Thread Hamish McIntyre-Bhatty
Hi all, Sorry for spamming the list a bit lately! :) Another issue I've had on my desktop, is that after being powered on for after maybe 4 hours, my memory usage starts to climb, but no process is listed as having used much memory. After a few days, this is what "free -h" shows: