Reduce KSplash loading time

[UriHerrera]

The Plasma login process starts after the user logs in from the display manager, in Netrunner's case, SDDM, by displaying KSplash. As noted by the README in its source repository, KSplash is part of Plasma itself, and it cannot be removed without patching Plasma. Here's its startup process:

Startup states:
===============

These are ksplash states:
- initial - at the beginning
- kded - after kded is running (dbus is ready, etc.)
- confupdate - after kconf_update (settings updated after upgrade, etc.)
- kcminit - after configuration setup
- ksmserver - session manager is started
- wm - window manager is running
- desktop - desktop (plasma) is running
- ready - session is ready (not fully actually, still e.g. restoring applications, but splash goes away)

To reduce the time spent by KSplash, I've done the following:

• Delete the unit files /usr/lib/systemd/user/plasma-ksplash-ready.service and /usr/lib/systemd/user/plasma-ksplash.service to prevent them from loading.
• Adjusting the ksplashrc entry in the Netrunner look and feel package to the following.

[KSplash]
Engine=none
Theme=none

Both of these changes manage to reduce the time spent by KSplash. However, in my tests with the following hardware:

P5G41T-M LX2/GB
Core 2 Quad Q9650 @2.0 Ghz (downclocked from 3.0 Ghz)
Radeon HD 4770
4GB DDR3 1333 Mhz
WD3200AAJS Hard-drive (DOM 20/02/08)

The lowest time I recorded was 42 seconds until the desktop completely loaded, a noticeable decrease from the original 2:40 minutes. This is still a considerable amount of time compared to using an SSD like the SV30037A/120G with the same hardware, where the process takes at most 4 seconds without deleting any service unit or editing the look and feel package.

[star-buck]

Do these 42 seconds start from hw power on or sddm log in?

…

On Tue, Jan 14, 2025, 13:14 Uri Herrera ***@***.***> wrote: The Plasma login process starts after the user logs in from the display manager, in Netrunner's case, SDDM, by displaying KSplash. As noted by the README in its source repository <https://invent.kde.org/plasma/plasma-workspace/-/tree/master/ksplash>, KSplash is part of Plasma itself and it cannot be removed without patching Plasma. Here's its startup process: Startup states: =============== These are ksplash states: - initial - at the beginning - kded - after kded is running (dbus is ready, etc.) - confupdate - after kconf_update (settings updated after upgrade, etc.) - kcminit - after configuration setup - ksmserver - session manager is started - wm - window manager is running - desktop - desktop (Plasma) is running - ready - session is ready (not fully actually, still, e.g., restoring applications, but splash goes away) To reduce the time spent by KSplash I've done the following: - Delete the unit files /usr/lib/systemd/user/plasma-ksplash-ready.service and /usr/lib/systemd/user/plasma-ksplash.service to prevent them from loading. - Adjusting the ksplashrc entry in the Netrunner look and feel package to the following. [KSplash] Engine=none Theme=none Both of these changes manage to reduce the time spent by KSplash. However, in my tests with the following hardware: P5G41T-M LX2/GB Core 2 Quad Q9650 @2.0 Ghz (downclocked from 3.0 Ghz) Radeon HD 4770 4GB DDR3 1333 Mhz WD3200AAJS Hard-drive (DOM 20/02/08) The lowest time I recorded was 42 seconds until the desktop completely loaded, which is a noticeable decrease form the original 2:40 minutes. — Reply to this email directly, view it on GitHub <#146>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGNDBRDDOBUYYNEAWB62FD2KT5SLAVCNFSM6AAAAABVEYB46OVHI2DSMVQWIX3LMV43ASLTON2WKOZSG44DMOJYGQ3DANA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>