Bug 339164 - Cpu monitor widget counts iowait as cpu load
Summary: Cpu monitor widget counts iowait as cpu load
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-systemmonitor (show other bugs)
Version: 4.11.11
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-18 07:47 UTC by Antonio Orefice
Modified: 2023-02-15 13:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio Orefice 2014-09-18 07:47:45 UTC
When i copy files over sshfs, cpu monitor widgets shows one cpu at 100%, but the cpu is not under load, because it is waiting for io operations to complete.


Reproducible: Always

Steps to Reproduce:
1. do some operation that generates iowait
2. observe the widget

Actual Results:  
one cpu is shown as under heavy load

Expected Results:  
it should not, ot at least the user should decide if it wants iowait calculated as cpu load
Comment 1 Antonio Orefice 2014-09-18 07:48:52 UTC
I don't know if  i choose the correct category, i'm speaking about the cpu monitor that does the cpu usage graph over time.
Comment 2 Nate Graham 2018-06-08 18:34:39 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham