Summary: | CPU load doesn't match values from top | ||
---|---|---|---|
Product: | [Unmaintained] ksysguard | Reporter: | Paul Cré <paulcre> |
Component: | ksysguard | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | rahul.vit2014, richard.llom |
Priority: | NOR | ||
Version First Reported In: | 5.12.6 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Paul Cré
2018-08-09 09:02:59 UTC
Did you take into account the update interval of top and ksysguard ? The values are pretty much(as far as I can match them visually) same if we set the update interval same on both. Tip:To change update interval in top press 's' or 'd'. (In reply to isalliswell from comment #1) > Did you take into account the update interval of top and ksysguard ? > The values are pretty much(as far as I can match them visually) same if we > set the update interval same on both. > > Tip:To change update interval in top press 's' or 'd'. Also I believe that I/O also adds to CPU load, which isn't tracked by top (since it is not a process) - however not sure about this. Furthermore, keep in mind that ksysguard isn't doing any calculations on it's own, but merely displaying a graph of the values in sysfs files. Setting to NEEDINFO. 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! 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! |