A few days ago I noticed that KDE Plasma was taking ages to launch. Like a minute or two of black screen as it loads, then a few more minutes of terrible slowness before things start to respond as they should. I assumed KDE was at fault and was just too bloated, until I recalled that my root partition was on an old 7200RPM HDD. I had completely forgotten since I dual boot and was primarily using Windows (which is on a separate SATA3 SSD) for the last few months.

So I replaced the HDD with an NVMe drive.


Cold boot to fully-responsive KDE in all its bloated majesty in less than 15 seconds.

  • 6
    Funny. Windows XP booted in 15 seconds on an IDE drive.

    And Windows 3.11 did it from drives of its age.

    And Windows 10 or a current Linux distributions does it from PCI SSDs. Fascinating, isn't it?

    I assume this is progress, isn't it?
  • 3
    I was using a 5400 RPM HDD as only harddisk until this week.
  • 3
    @Fast-Nop Same, and I hate Systemd with passion for not allowing me to configure load order without messing up dependencies, and for being way too complex to be replaced.
  • 0
    Hm, I have no problem with KDE at all.

    Slow start usually means a service isn't working as intended, since the splash only stops when all services reported successful start or a fixed timeout.

    I3M and other window managers will definitely be faster, since they don't use eg DBUS / services / and so on.

    Except you configure them to autostart ;)
  • 0

    They've reduced the timeout to 15 sec sometime ago If I remember correctly
  • 0
    @IntrusionCM Hmm. I didn't have anything in autostart other than ksuperkey. Not sure why the splash screen took so long, but even after my desktop loaded, it would still run extremely slowly for the first couple of minutes. I never could figure out what it was doing in the background during that period of lag. Perhaps there was something wrong with the HDD itself.

    Regardless, that slowness is gone now.
Add Comment