You are not logged in.

#1 2025-06-07 11:01

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 5,007
Website

Memory usage of desktop environments in Q4OS

We have performed memory usage tests in various desktop environments running on the Q4OS 5 Aquarius operating system.

Steps to reproduce for anyone to try:
- Install Q4OS 5.8 Aquarius Plasma 64bit, Basic profile in Virtualbox_7.1.10/2GB RAM/64bit
- Install all desktop environments in question using Desktop profiler
- Reboot and login to each desktop session for the first time
- Run "htop" tool and wait for OS to settle down
- Read the memory usage by htop [1st] at 4:00 uptime
- Reboot and login to each desktop session the second time
- Run "htop" tool and wait for OS to settle down
- Read the memory usage by htop [2nd] at 4:00 uptime

Results: [2nd/1st] time login in MB:
- IceWM .. 288/294
- Openbox .. 346/355
- Trinity .. 421/422
- LXDE .. 436/449
- LXQt .. 539/540
- Plasma .. 740/775

Offline

#2 2025-06-07 18:51

crosscourt
Member
From: Wash DC
Registered: 2017-05-07
Posts: 2,372

Re: Memory usage of desktop environments in Q4OS

Using your methodology(I didnt run in VB, actual installs, full desktop of these DEs) I can confirm the numbers for Trinity, LXDE and Plasma, Heres my results,

Trinity- 424/429
LXDE-440/450
Plasma-741/777

I was interested in your results with LXQT, as many see it as a lightweight DE but in fact its not.


Q4OS KDE 5.xx  Lenovo M73 Thinkcentre Tiny/Dell Inspiron 3670

Offline

#3 2025-06-07 20:28

josek
Member
Registered: 2025-02-23
Posts: 49

Re: Memory usage of desktop environments in Q4OS

"My search for the lightest Linux desktop environment led me to explore options like IceWM and LXDE. While they are extremely resource-efficient, allowing me to boot with only 200MB of RAM (the lowest I could optimize), their configuration leaves a lot to be desired.

I found that basic and essential tasks became a real struggle to get them working properly:

Brightness Management: Adjusting the screen brightness, something so fundamental on a laptop, became a challenge.
Screenshots: The screenshot functionality wasn't as straightforward or intuitive as one might expect.
ACPI Events: This is where the experience became more complex. Managing lid closure, hibernation, and battery management required manual configuration and often intervention in system files to ensure they worked reliably, without freezing or failing to respond as expected. This was precisely a critical point we experienced, where the lack of integrated ACPI management caused A slow and problematic shutdown when closing the lid, forcing me to investigate the systemd-logind logs and configurations to resolve it.
Bluetooth Volume Control: Connecting and managing the volume of Bluetooth devices was another point of friction, which involved a more laborious configuration for something that should be plug-and-play.
In contrast to these experiences, I was pleasantly surprised by TDE Trinity. Although it initially seemed like it would consume more resources, I managed to optimize it to only 300MB of RAM (obviously, after carefully removing unnecessary services and programs, a process we also explored in depth).

Trinity's great advantage is that, despite consuming those additional 100MB, it is much more complete and simpler to use on a daily basis. All those settings that in IceWM and LXDE required searching and complex manual configurations, Trinity handles them fluidly and directly through its Control Center. Its power, ACPI event, and hardware management are robust and functional out of the box, more than offsetting that small difference in power consumption. RAM with unmatched stability and ease of use.

Ultimately, while IceWM and LXDE are the kings of pure lightness, their incomplete configuration and the constant need to "dig" for solutions for basic functionality don't make up for the lack of integration and simplicity that Trinity offers. TDE proves that you can be efficient without sacrificing convenience or essential functionality.

Offline

#4 2025-06-07 21:09

crosscourt
Member
From: Wash DC
Registered: 2017-05-07
Posts: 2,372

Re: Memory usage of desktop environments in Q4OS

Totally agree, josek

Last edited by crosscourt (2025-06-07 21:50)


Q4OS KDE 5.xx  Lenovo M73 Thinkcentre Tiny/Dell Inspiron 3670

Offline

#5 2025-06-08 13:16

Midas
Member
Registered: 2017-12-15
Posts: 234

Re: Memory usage of desktop environments in Q4OS

josek wrote:

Ultimately, while IceWM and LXDE are the kings of pure lightness, their incomplete configuration and the constant need to "dig" for solutions for basic functionality don't make up for the lack of integration and simplicity that Trinity offers. TDE proves that you can be efficient without sacrificing convenience or essential functionality.

This is an insightful piece of analysis. Thanks. cool

Offline

#6 2025-06-08 19:46

crosscourt
Member
From: Wash DC
Registered: 2017-05-07
Posts: 2,372

Re: Memory usage of desktop environments in Q4OS

There are some distros though that have done a great job of overcoming limitations with lightweight DEs like iceWM with antiX and LXDE with LXLE.

Trinity with its design will suit more users overall.


Q4OS KDE 5.xx  Lenovo M73 Thinkcentre Tiny/Dell Inspiron 3670

Offline

Board footer

Powered by FluxBB