Bug 440329 - CPU usage shown, not the same of other task managers
Summary: CPU usage shown, not the same of other task managers
Status: RESOLVED UNMAINTAINED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: general (show other bugs)
Version: 5.22.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-07-27 13:46 UTC by Germano Massullo
Modified: 2024-09-23 20:59 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot (75.06 KB, image/jpeg)
2021-07-27 13:46 UTC, Germano Massullo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Germano Massullo 2021-07-27 13:46:48 UTC
Created attachment 140353 [details]
screenshot

See attached screenshot
Ksysguard showed CPU cores at 100% usage, but other task managers like htop showed a much less CPU cores usage. Why there is this asymmetry?

Ksysguard 5.22.0
KDE Frameworks 5.83.0
Qt 5.15.2
Wayland session
Comment 1 Germano Massullo 2021-07-27 13:48:10 UTC
You could say "it's just a peak", no it was a thing that was going on during all the time I left Ksysguard opened
Comment 2 Nate Graham 2021-07-28 13:59:06 UTC
What do `top` and the old ksysguard say? Are they all different, or is System Monitor the only one that disagrees with all the others?
Comment 3 Germano Massullo 2021-07-28 15:32:47 UTC
(In reply to Nate Graham from comment #2)
> What do `top` and the old ksysguard say? Are they all different, or is
> System Monitor the only one that disagrees with all the others?

What is the "old ksysguard"?
Comment 4 Nate Graham 2021-07-28 15:45:46 UTC
Oh you are using the old ksysguard lol.

Is the CPU graph better in the new System Monitor app?
Comment 5 Bug Janitor Service 2021-08-12 04:36:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2021-08-27 04:36:45 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 7 Germano Massullo 2021-08-27 10:50:55 UTC
(In reply to Nate Graham from comment #4)
> Oh you are using the old ksysguard lol.
> 
> Is the CPU graph better in the new System Monitor app?

What is the name of the executable of the new system monitor application?
Comment 8 Nate Graham 2021-08-27 16:13:43 UTC
It doesn't matter because this bug report *is* about the old one.
Comment 9 Germano Massullo 2021-08-30 10:43:24 UTC
(In reply to Nate Graham from comment #8)
> It doesn't matter because this bug report *is* about the old one.

I asked because I wanted to install it. The time you spent writing this message could have been used to just write the name of the new application
Comment 10 Nate Graham 2021-08-30 13:51:27 UTC
The new one has its own Bugzilla component; bugs for the two separate apps are tracked separately.
Comment 11 Christoph Cullmann 2024-09-23 20:59:51 UTC
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task.

If your issue still happens with the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!