5 ms·
XFCE is a pretty snappy desktop interface, sure, however KDE is not less snappy than XFCE. I have used both more than >5 years, at the same time. KDE was on a m
by bayindirh 4y ago
XFCE is a pretty snappy desktop interface, sure, however KDE is not less snappy than XFCE. I have used both more than >5 years, at the same time. KDE was on a much slower system and was not visibly slow w.r.t. XFCE. Now I'm using KDE everywhere.
The perceived slowness is due to window effects in KDE. Disable these and window appear before you lift your finger from your mouse or enter key.
Lastly, KDE's memory usage comes from the facilities it provides. Disable them if you don't need them, and save a lot of memory. KWin (window manager + compositor) uses ~180MB on a 4K screen, while file manager needs another 57. That's not much.
- nyanpasu64 4y agoplasmashell, which is written in QML (JS-based), uses hundreds of megabytes, and sometimes leaks memory or bugs out (as far as I can tell, the leaking and instability/crashing is an interaction between QML/JS, the JS engine, and KDE's C++ classes exposed to JS through bindings).
- bayindirh 4y agoAfter a week of uptime, plasmashell is consuming 350MB memory (taken just now from my process manager). Considering this is my work machine and I never reboot except kernel updates, I've never seen it leak memory or crash tho. This is Debian Testing with KDE 5.26.4 w/ Frameworks 5.100 w/ Qt 5.15. 350MB is not very optimal of course. I may dig the code to see the reasons, tho. XFCE4 had a similar memory leak ~2 years ago, which was triggered every time screen went into sleep and came back. So, bugs & shenanigans happens, but I'm not still sure that KDE is "hell of a bloat" considering the things it provides at the speed it provides.
- nyanpasu64 4y agoChecking coredumpctl, I've gotten two plasmashell segfaults in the past 4 months, and recall hangs and crashes happening more often in the past (especially under NVIDIA drivers). Additionally plasmashell has hung a few times and/or kwin terminated unexpectedly, though I think this is a Mesa bug (https://www.reddit.com/r/kde/comments/zbux1i/where_would_i_start_looking_to_debug_random_kwin/ https://www.reddit.com/r/kde/comments/zbux1i/where_would_i_s..., https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674) or amdgpu kernel bug (I've had multiple GPU driver hangs and unusable screens on sleep-wake, usually preceded by kwin dying in the same session).
- bayindirh 4y agoI also checked coredumpctl, and no KDE related crashes logged there, hence validating my experience. Funnily, both my desktop systems run on NVIDIA cards w/ NVIDIA drivers, and both have uptime numbers in multiple months at minimum. The personal desktop I used to use was regularly suspended to RAM and woke back, and my work system is on 7/24. Both are running KDE, and never misbehaved. They are not lightly used systems either. Also both installations use KDE extensively. Akonadi, Baloo, KIO, etc. are regularly used. At the end of the day, this is strange.
- kstenerud 4y agoI did extensive testing of various desktop environments, and KDE was consistently the most sluggish of the bunch (tested across multiple devices), even after disabling all of the eye candy. The next worst is Gnome. XFCE is snappy, but annoying due to the 1 pixel window border that you can't ever click on a high DPI display. Mate is almost as snappy and has better UX, so I use that.
- bayindirh 4y agoIf you can share your test methodology, I can reproduce your results and can see for myself. My personal experience doesn't mirror what you have said, but sharing personal experiences do not bring us to an objective truth. I use ALT+ (R/L) click for move resize, so I never interact with borders of windows for a very long time, honestly.
- hnlmorg 4y agoI run KDE on an old Intel NUK. It’s got 4GB RAM, 32GB SSD and a decade old i3. KDE still flies on that system. The only time I’ve found KDE not feel responsive was in Kubuntu. I have no idea what is different about Kubuntu vs other Linux distros but the slowness in KDE on Ubuntu is down to Ubuntu and not KDE.
- doubled112 4y agoI've found that a barebones KDE is fast, but KDE with Akonadi and file indexing is resource intensive, especially until everything is indexed.
- bayindirh 4y agoWhen baloo finishes indexing its load on processor is practically zero. Akonadi is just a centralized account management framework which works on events coming from these accounts. Baloo uses a lot of RAM depending on what you index, but neither Akkonadi, nor baloo takes custody of the processor(s) and degrade system performance.
- bmn__ 4y ago> Disable [the features] if you don't need them, and save a lot of memory. This is not possible in reality. https://news.ycombinator.com/item?id=24503435 https://news.ycombinator.com/item?id=24503435
- bayindirh 4y agoIt seems, the user either has some big problems on his KDE installation or looking to shared memory usage, to begin with. Let's see what I have in the same list: 157M kwin_x11 (window manager) 392M plasmashell (desktop shell, widgets and other on screen tools) 175M krunner (macOS spotlight equivalent) 30M kded5 (settings and background daemon) 10M kactivitymanagerd (multiple activity contexts) 40M polkit-kde-authentication-agent-1 (KDE polkit bridge)) 25M org_kde_powerdevil (energy settings) 19M kdeconnectd (use mobile phone as remote control) 5M xembedsniproxy (make tray icons work) 13M kaccess (accessibility keys?) 16M ksmserver (Plasma session manager) 41M plasma-browser-integration-host (Firefox can show desktop notifications) 10M kwalletd (password manager) 6M kglobalaccel5 (global keyboard combos) 5M kscreen_backend_launcher (changing screen orientation and resolution?) 2M kio_http_cache_cleaner (?) 32K xsettingsd (apply colour scheme to Gnome applications) (Some lines omitted since they are not running on my system) On uninstalling/disabling things: - There's background services menu, which you can control which services to load. - Baloo can be completely disabled by disabling file search. - Akonadi is just "Online accounts". Add nothing, it consumes nothing. - KRunner runs on plugins. You can disable any and every plugin, which will reduce its memory footprint too. - You can uninstall any KDE feature package (at least in Debian), and these features will magically disappear from KDE interfaces. Lastly, as another user noted, KDE and Qt has a self-resizing magic, and will try to minimize its memory footprint when the system has low memory. So, you can run KDE on a 4GB system and a 32GB system. KDE will allocate more in the second system, but will evict as much as possible as the memory load increases. Witnessed this in a professional project where we ran KDE on extremely limited thin clients and saw how it behaves.
- bmn__ 4y ago> You can uninstall any KDE feature package (at least in Debian), and these features will magically disappear from KDE interfaces. You didn't actually try this. It makes me annoyed that you think you can go on the internet and just claim something and expect it not be verified; what a bunch of nonsense. In Debian 11.5, when one tries to uninstall any of kactivitymanagerd, polkit-kde, kaccess, then the package manager also takes out KDE as a whole.
- floren 4y agoI decided to give KDE a shot again after over a decade running minimal window managers, and while I really like the interface, it occasionally just freezes the entire system for multiple seconds at a time. Screen stops updating, mouse and keyboard don't do anything. This is on an i7 laptop with 16 GB of memory. This never happened under StumpWM.
- bayindirh 4y agoThis is very unusual of KDE, I never experienced anything like that in the last decade. I mean, since (and including) KDE 3.5.x, yet alone 5.