Version: unspecified (using KDE 4.4.5) OS: Linux Hello, when I have heavy pressure on disk activities (4x copy of heavy file or folder), all kde is slow down, same writing in text editor like kwrite. Thanks to minimize for the future version the disk access for the interface (menu, windows changing mainly with konsole with composing background, write in text editor, ...) My wish it's have very reactive system like windows when disk is heavy used. Reproducible: Always
Could it be related to http://www.phoronix.com/scan.php?page=news_item&px=ODQ3OQ ?
Yes it's possible. I do very frequenly copy, KDE under windows not slow down but under linux slow down. And it's crazy of lag into text writing or input writing...
KDE is not usable in version 4.4.5 too with old hdd of 20GB. And on my system (8GB memory, 2TB of hdd, quad core), the menu after long time have difficult for open it. (Keep all entry except icon into memory for improve the speed and update only via event like inotify or solid, for have any hdd access when try open the menu)
Is this still a problem in recent versions of Plasma 5, like 5.19 or later? Note that we are working on a generic solution to this issue via systemd slices and cgroups, which will allow us to boost the CPP and IO priority of the frontmost app, preventing these kinds of frustrating hangs and freezes.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!