3 ms·
Ah, some good food for thought for those new Linux users that have no understanding of software engineering and caching. Because most engineers know that memor
by sph 4y ago
Ah, some good food for thought for those new Linux users that have no understanding of software engineering and caching.
Because most engineers know that memory usage of different pieces of software does not mean very much. It is very possible that that a DE boots into 100 MB, and then it's usage grows to absurd level while it is being used due to poor coding or architectural practices, while another DE might use 500 MB at boot, and then not increase very much because all its core logic is contained within this amount of memory.
Many enthusiastic people entering the Linux world, the type that run neofetch and post it on Reddit every time they jump to a new distro, are always really interested in the RAM usage figures, as if they were a real indicator of "bloat".
While I immensely appreciate how clearly it defines the methodology of this comparison, posts like this are a good way of keeping that dumb practice of running `free` after boot and drawing conclusions alive.
- wjnc 4y agoExactly. Please, pretty please, use all my memory for even trivial tasks. Just make my system snappy and carry me while under load. I've got 16 cores, please use them. Use them a little bit smartly since I pay for power. Perhaps, don't write as much as you could since my SSD is the first part to die. The most memorable increase in happiness for me was when Ubuntu Gnome went fully high refresh rate. Things just felt faster after that. I'm pretty sure that is nowhere near the same ballpark as the HDD-SSD transition of a decade ago. And still, it's feeling that counts. (I do look back fondly on the whole optimizing Windows XP installer to 42MB of a few decades hence, but that's not where productive people go.)
- itvision 4y agoI did _not_ just run `free` after boot, maybe you need to reread the methodology. As for RAM leaking - I cannot and I will not account for that: such a test could take weeks to carry out. In my experience modern Linux DEs do not leak that much - people normally do not interact with their DE (yeah, I'm not joking) anyways - you boot into something, e.g. Gnome and you run your applications (e.g. web browser, spreadsheet, terminal emulator, media player, instant messenger, etc. etc. etc.) and your DE is running happily in background.
- sph 4y agoYou interact with your DE whenever you create a window, switch to another, press the Super button, right click on the desktop, get a popup notification, hit your media keys, and in a decreasing way the more you move towards the Window Manager end of the spectrum. So of course I would expect fluxbox to use less memory than KDE, because fluxbox doesn't do anything if I press the volume keys (please correct me if I'm wrong, I haven't used it in a decade) Does that mean that fluxbox and all of its associated tools are going to be as snappy during real usage? You can't certainly know by just analysing the RSS and shared memory size of the fluxbox process.
- itvision 4y ago> You interact with your DE whenever you create a window, switch to another, press the Super button, right click on the desktop, get a popup notification, hit your media keys, and in a decreasing way the more you move towards the Window Manager end of the spectrum. Most of this is handled by a window manager. Again, most users launch their favourite set of applications at the start of the day and run them until (if) they log off. And the average programmer is no different: a web browser, IDE, terminal emulator, Telegram and Slack all running non-stop.
- sph 4y agoIt's not so clear cut. Your kwin process uses the KDE libraries and facilities, some of which are used by Dolphin as well. It's a mesh of interconnected and communicating processes via IPC, unix sockets or shared libraries, not standalone islands. Firefox might show a native printing dialog that's exposed in some core code loaded when you logged in. In fact the line between DE and WM on a bigger desktop gets blurrier, especially in the Wayland era when your WM is actually also your compositor, so handles all your windows and their positioning, input dispatch, permissions, etc.
- itvision 4y agoIf we go down this route no comparison will ever be "valid". That's why this is strictly for Fedora 37 as of December 11th, 2022. :-) If you have your own distro resuts to share, I will happily add them to the article.
- pmontra 4y agoI remember sysadms in the company I was working for 20+ years ago. They've been managing HPUX and Solaris systems forever and we suddenly added a bunch of Linux servers for an application delivered by my team. They gave me a call one day. "Those Linux machines were at 100% RAM so we doubled it. They are still at 100% RAM. What's your software doing?" I guessed that the system management software on HPUX and Solaris was clearer about the distinction between memory used by applications and memory used by the file system cache, because I remember that file system cache was a thing even in HPUX and all the other UNIX flavors I used at university ten years before.
- sph 4y agoIndeed. Free RAM is useless RAM and a waste of actual money. If everything I use is magically always in RAM with no swapping ever, I don't care if I'm constantly at 100% usage. That's what I bought it for. We're lucky we are unable (AFAICT) to have real stats on L2 and L3 cache recency utilisation.
- krageon 4y agoI would say most engineers know high memory usage without a clear cause correlates strongly with poorly written software, it's likely to be slow and shit.
- whalesalad 4y agoAs a long time Linux user I can appreciate what you are trying to communicate here - but it comes off as kind of abrasive and harsh. Those kids playing with their machines, running neofetch, 'ricing' their desktop - they are the future of this ecosystem. You can either alienate them or try to shepherd them, I think we need to try the latter.