Bug 412884 - Excessive precision in I/O graphs; usability;
Summary: Excessive precision in I/O graphs; usability;
Status: RESOLVED FIXED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (other bugs)
Version First Reported In: 5.15.5
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2019-10-12 17:36 UTC by Amin
Modified: 2021-09-13 21:51 UTC (History)
0 users

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

Attachments
excessive 6 digits after dot in ksysguard when I/O meter (12.18 KB, image/png)
2019-10-12 17:36 UTC, Amin 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Amin 2019-10-12 17:36:51 UTC 
Created attachment 123166 [details]
excessive 6 digits after dot in ksysguard when I/O meter

SUMMARY

When monitoring I/O activity, current values of data from sensors like disk/sd*/Rate/rblk or disk/sd*/Rate/wblk show with unreal precision - 6 digits after dot. 

STEPS TO REPRODUCE
1. Add new tab and graph with disk/sd*/Rate/rblk sensor
2. Watch current values with 6 digitls after dot.


OBSERVED RESULT
Too excessive precision for current values of this data.

EXPECTED RESULT
Smart round of values.
If we have 125800.569226 Kb/sec of read data, last 6 digits absolutely trash.
125.8 Mb/sec more comfortable for read value.
But for very small values (floppy ?) (for example less 15 Kb/sec) all digits can be showed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 30
KDE Plasma Version: KDE Frameworks 5.59.0
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.5

ADDITIONAL INFORMATION
This not "bug", this interface usability idea.
Comment 1 Amin 2021-09-13 21:51:38 UTC 
fixed in 5.22.0