![]() Registered Member ![]()
|
Okay, here is what's bugging me...
1. KDE pretty dependably takes 20+ seconds to start, and longer from a cold boot. There's a lot of disk activity when starting after a cold boot, but subsequent startups still take a long time, despite showing little disk activity. 2. The slower the computer, the slower the start time. Startup takes over a minute on an 800 MHz single-core machine. 3. Disabling most services does not help; nor does disabling Nepomuk, Akonadi, and Strigi. Disabling power management and mounting services makes a difference on some versions of KDE, but not others. Disabling debug output and logging does nothing either. Pulseaudio is not involved at all (I'm not using it). I figure something must be wrong, because not everyone who uses KDE (even on low-end hardware) seems to be bothered by this... Either that or most users have much more patience than me when dealing with slow login times. The following is my .xsession-errors file. Most services were disabled during the session when this was created, as were Nepomuk and Strigi:
The only thing that seems odd to me here is that kbuildsycoca4 seems to run four times, but I'm no expert on KDE... Does anything look odd here? (FWIW, the vblank_mode thing is because I have manually overridden sync-to-vblank, as it doesn't work right with the Intel driver.) TIA! Edit: No, I hadn't tried disabling Plasma yet. My bad. |
![]() Administrator ![]()
|
kbuildsycoca4 should only be being run once - not 4 times. kbuildsycoca4 is a very disk intensive process, which may explain why it takes so long.
Can you reproduce this observation?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Unfortunately I'm having some trouble reproducing this, not sure why. Even without kbuildsycoca4 being called repeatedly, KDE is very slow to start.
OTOH, I will say that I have yet to see any computer on which KDE starts in 10 seconds or less, and that includes a Core 2 Duo workstation with 4 GB of RAM. Also, I should mention that (by my wall clock) I get comparable 20+ second start times from Unity (both 2D and 3D) and Gnome 3, so I'm beginning to think that (again) newer desktop environments in general are nonviable for low-end computers. Maybe it's just a question of too many lines of code being executed. |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot]