> On Okt. 5, 2014, 10:29 vorm., Milian Wolff wrote: > > Hmm... there is no way to see the wait time anywhere then, right? I don't > > see a way to add individual columns for that. Maybe that should be > > re-thought for frameworks. I.e. keep the CPU% like now but add more columns > > for the individual cpu/wait times? > > Søren Holm wrote: > That's right. But fact is that IO-wait is not time actually used. It's > just a clasification of the idle cpu time.
Notice that it is NOT included in the idle time, though. I don't know the code in question, but assume it needs to be added to the idletime somewhere? - Thomas ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/120406/#review67948 ----------------------------------------------------------- On Sept. 28, 2014, 3:07 nachm., Søren Holm wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://git.reviewboard.kde.org/r/120406/ > ----------------------------------------------------------- > > (Updated Sept. 28, 2014, 3:07 nachm.) > > > Review request for kde-workspace. > > > Repository: kde-workspace > > > Description > ------- > > IO-wait is included in the cpu usage. This is wrong since IO-wait is a part > of the idle time. This goes for both total combines CPU-usage and the per CPU > usage. > > > Diffs > ----- > > ksysguard/ksysguardd/Linux/stat.c 534a465 > > Diff: https://git.reviewboard.kde.org/r/120406/diff/ > > > Testing > ------- > > Fx. running a read from a slow USB-media like this will always end up showing > 25% load on my system (I have 4 cores) > > dd if=/dev/sdb of=/dev/null bs=1M > > This end up being around 0% with my patch. > > > Thanks, > > Søren Holm > >
