Thanks I’ll give 5.14 a shot later just to see what happens, as others mentioned the RAM usage itself might not be an issue in itself overall. I’ve stuck with LTS kernels only for some time now after some troubles I had way back. Can’t remember what, but I’m running 10-14 year old laptops… once the top models in their class, but now long in the tooth and bought cheap
I don’t have the knowledge to understand the repercussions of this off the top of my head, but thanks for the tip!
I’ve checked this on Xfce installed on VM, and it looks the same, those are sub-processes (I’m just stupid). However, RAM usage is normal, around 600 MiB (didn’t update VM yet).
I’ve checked 5.4 and 4.19 kernels, and they also have different RAM usage. Lowest is 5.10, at least on my potato.
heh, I misread this and your earlier post, I thought 5.14 was lowest. As I have plenty of RAM and saw a few glitches with 5.14 mentioned in the stable update thread I think I’ll just leave everything as is for now. 5.10 LTS. thanks again!
Data posted for the ‘road machine’ shows an uptime of 27m and may not be relevant to RAM use when first booted. But this data also shows only 158 active processes
Data for the ‘long time’ system is showing an uptime of 1m, but is also showing 2 wakeups
and 253 active processes
I rebooted my main system to get more data from free and inxi
total used free shared buff/cache available
Mem: 7.7Gi 536Mi 6.7Gi 4.0Mi 510Mi 7.0Gi
Swap: 3.9Gi 0B 3.9Gi
No packages were updated or changed since previous boot but system reports 2 MiB less than before
Based on the comments here and my own experimentation, it is clear that tools like htop/task manager understand “ram usage” differently compared to free
After making this post, I downloaded the ISO and did a clean reinstall so that I can compare the differences before and after the latest update. Here is a summary of what I discovered:
After the reinstall, htop reported 680MB initial RAM usage before I ran a system update.
After running the system update, htop reported 1.1GB RAM usage.
The results of the free command were consistent both before and after the system update. free -h reported around 590MiB RAM usage for both cases.
I think the best way to resolve this is to find out what htop considers as “ram usage.” Since free returned the same result before and after the latest stable update, it’s likely that the new update doesn’t use more RAM, just that somehow htop is reporting that it is using more.
I think this is the best possible answer based on limited data available
To get a more specific answer would require a lot of testing
User would have to start with an old ISO running v5.10 kernel, as already suggested
system would have to be cold-booted about 10 times to get an average of values from inxi and free
(values for RAM used can vary even when no changes are made to system)
Then system can be updated and repeat tests to get new data values
And for a thorough job the kernel should be updated to v5.14 and repeat tests for the later kernel
But considering that none of the comments here mention the usual consequences of having additional processes loaded and more RAM used (increase in time taken to boot or less responsive desktop) this seems like a lot of effort for not much gain
@omano Yes, that appears to be the case. Before this, I assumed that the memory reported in htop is the same as the one in free. But I was clearly mistaken. I am still rather curious about the difference though, even though that knowledge might not have any practical value other than to save beginners some unnecessary confusion about RAM usage.
If you want more to think about, explain me this now lol (this is why I posted my previous reply, the following image is from another thread where I found out this):
Different tools, different results, most of them not making sense (especially the KDE tools, my conclusion was that they are garbage, and opening tickets on KDE seems to be useless, based on my short experience where they ‘fixed’ another bug I reported regarding the hard drive space used, but it didn’t fix anything, and they got silenced when I tried to have this looked at again so I don’t bother I count on people more motivated than me to get things fixed).
free seems to be reliable, other tools are approximative.
Some interesting reading ahead, thanks, I’ll be looking into this… first I’d heard of ‘free’. As a beginner, speaking anecdotally, I started habitually loading HTOP immediately after any reboot for about a year now. I run humongous Firefox sessions and had to keep an eye on resources lest my system freeze up before properly saving a session. No longer much of a problem now that I’ve jumped from 8 to 16, now 32GB of ram.
Anyway, that htop “mem” figure was what I was keeping an eye on. Lets say at least 40 reboots over a year, whatever it actually means mem has always been around 600 at boot. After the last update, immediately after booting and loading htop, it went to 1000+. Just rebooted for the sake of science
It was one of the first post, but just in case, good information are there. Good to read it to understand more how it works.
Maybe some updated programs make the system cache more things than before, but still look at the real memory used, with free, or htop with the other RAM meter (not the bar one, but the detailed text one
Seconded. I like this answer. And in case anyone is wondering how to change the bar style to numbers style: just go to options in htop, select meters, switch to the memory meter and hit space to change the style of the display.