4 ms·

The only problem I ever had with KDE is it randomly hogging the CPU. On different machines, same problem. And not just for a minute, but 10+. Still not sure wha

by jotm 5y ago

The only problem I ever had with KDE is it randomly hogging the CPU. On different machines, same problem. And not just for a minute, but 10+. Still not sure what the reason was, that was Fedora 24 to 30 and some random Kubuntu between (yep, all had that problem randomly). Maybe it's fixed these days. GNOME just got worse and worse lol

simion314 5y ago
>The only problem I ever had with KDE is it randomly hogging the CPU. Can you be more specific, like what process exactly did that?
- rhn_mk1 5y ago
  Not OP, but plasmashell, activitymanagerd, recently krunner. The first two because I have a sshfs mount, the latter only recently for no good reason.
  - simion314 5y ago
    >Not OP, but plasmashell, activitymanagerd, recently krunner. The first two because I have a sshfs mount, the latter only recently for no good reason. I don't doubt you, I never had performance issue with my KDE though I always run LTS Kubuntu. I am wondering why plasma or activity monitor would have issues with your filesystem.
    - rhn_mk1 5y ago
      My guess is that they query a service that does file operations for no good reason, and then busy wait for it.
zorr 5y ago
When my machines were doing that on Plasma it was typically the Baloo file indexing or some Akonadi related process that was going crazy on the CPU. This week I switched back to Gnome Shell after a few years of Plasma on my main desktop and I must say it feels a lot more responsive than Plasma.
- michaelmrose 5y ago
  You are absolutely correct of file indexing and it was true of the prior iteration Nepomuk. It is seemingly a complex thing to get right. File indexing sucks hard in several instances - When the OS is running on the same spinning rust or performance is substantially impacted by said rusts performance - When the filesystem uses encryption but isn't hardware accelerated - On first run when it has to index everything - If the filesystem performs poorly on lots of small files. So you boot up on a fresh install do you just not showcase features working to their fullest or do you sink performance for the first hour or hours on some systems much more than others? I think personally you ought to prompt the user to schedule the first run of the file indexing service since it will impact performance far more initially than it will thereafter.

by jotm 5y ago

simion314 5y ago

>The only problem I ever had with KDE is it randomly hogging the CPU. Can you be more specific, like what process exactly did that?

rhn_mk1 5y ago
Not OP, but plasmashell, activitymanagerd, recently krunner. The first two because I have a sshfs mount, the latter only recently for no good reason.
- simion314 5y ago
  >Not OP, but plasmashell, activitymanagerd, recently krunner. The first two because I have a sshfs mount, the latter only recently for no good reason. I don't doubt you, I never had performance issue with my KDE though I always run LTS Kubuntu. I am wondering why plasma or activity monitor would have issues with your filesystem.
  - rhn_mk1 5y ago
    My guess is that they query a service that does file operations for no good reason, and then busy wait for it.

zorr 5y ago

When my machines were doing that on Plasma it was typically the Baloo file indexing or some Akonadi related process that was going crazy on the CPU. This week I switched back to Gnome Shell after a few years of Plasma on my main desktop and I must say it feels a lot more responsive than Plasma.

michaelmrose 5y ago
You are absolutely correct of file indexing and it was true of the prior iteration Nepomuk. It is seemingly a complex thing to get right. File indexing sucks hard in several instances - When the OS is running on the same spinning rust or performance is substantially impacted by said rusts performance - When the filesystem uses encryption but isn't hardware accelerated - On first run when it has to index everything - If the filesystem performs poorly on lots of small files. So you boot up on a fresh install do you just not showcase features working to their fullest or do you sink performance for the first hour or hours on some systems much more than others? I think personally you ought to prompt the user to schedule the first run of the file indexing service since it will impact performance far more initially than it will thereafter.