Plasma extremely slow just after boot and high disk usage
Page 1 of 1 (5 posts)
Tags:
None
Registered Member 
|
Some times, randomly, when I boot the system and login, the plasmashell session is unusable because of lag. Trying to open the main menu or a window in the task manager is impossible.
This comes with a very high disk usage of the root disk by plasmashell process, which makes that disk also unusable. The CPU usage of that process is also a bit higher that it should be. I don't know what is plasmashell doing to consume all that disk and CPU, but when I kill plasmashell process, everything returns to normal. That said, if I try to run it again, everything starts to lag again. All the windows, the mouse, the browser... everything works fine but the plasma things (dock, desktop, app menu...). And if I just wait without killing plasmashell, after a couple minutes it randomly fixes everything and the desktop becomes usable... Again, this whole problem only happens "some times", randomly, which makes it harder to detect what's causing it. This is the output of plasmashell:
And this is the output of lsof -p (pid of plasmashell) with all the files the process could be using to cause the high disk usage:
Things I've tried: - Removing plasma cache - Removing all applets - Unmounting all disks but the root one |
|
Registered Member
|
I want to assume that you are using an HDD. If so, it usually takes about 15-20s for Plasma to be completely ready (assuming you have a reasonable amount of auto-started applications.) The behavior you describe above is not normal, as the files listed are the typical stuff that gets read (the ~/.config/ files aren't listed though...). It smells like a 'HDD sector/block failure' or 'corrupted file system' scenario. Run a SMART test, get software like DiskMonitor, Gnome Disks or GParted(?) and check the SMART readings of the drive. See if anything screams 'BAD' or 'WARNING'. If you don't see anything, do a file system check, I don't know which filesystem you are using.
|
|
Registered Member
|
I don't use an HDD and I ran a SMART test not long time ago and I didn't get any error. I know that in an HDD, it could take time to boot, but 15 minutes?... I don't think so. This problem is not like "it's slow at boot", it's "extremely slow after boot", the system is ready to use like 5-10 seconds after I login, it has booted already, but plasmashell is lagged for some minutes after the login. The system is responsive, I can open Dolphin, go through folders, open files, open firefox... but the dock, and all plasma related apps are unusable because of lag (like 5 seconds between a click and a response from the program). All my disks are ok, I can confirm, also this problem has been there before and after I updated the root disk (I moved the root partition from the old disk to the new one, and in both of them I had the lag at boot). And I use ext4. |
Registered Member
|
Check for heavy disk usage. Baloo file search is one thing to look at, but it could be something else.
Also check swap usage. Some systems in my experience seem to like to hit swap far too early for some reason, even with plenty of ram. This 'swappiness' can be adjusted. Exactly how may depend on the actual OS.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
|
Registered Member
|
The process using disk was plasmashell, not baloo. Baloo is a different process and it was idle. Also, when baloo starts indexing I see it uses a little bit of disk and CPU, but not so much that it lags the entire desktop, it works fine. And about the swap... I have the default 60 swapiness and when this happens, it's not using a single mb since it just booted and the ram usage is like ~950mb (I have 16gb). |
Page 1 of 1 (5 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]
