Incorrect summarization for kilobytes received/send

[drowsytech]

Hi,

As you can see from the attached screenshot on Y axis the summarization is incorrect, it doesn't provide any indicator that those values are in thousands. A better improvement might be to calculate and show mbps data as that would be much useful.

[iamsureshraju]

Hi,

As per the manual, the values are represented in kb/s. Could you please advise which is incorrect. Do you mean calculate it by 1024 instead of 1000?

rxkB/s - Total number of kilobytes received per second.
txkB/s - Total number of kilobytes transmitted per second.

[drowsytech]

Hi Suresh, These are kilobytes so that would be kB/s not kb/s. Another thing is the counts on the graph is in thousands, but Y-axis doesn't reflect that. Also another was a suggestion do do some magic and instead of showing kB/s insted show mbps (mega bits) as that will make it more helpful to read. By the way, great work on the tool. Really helpful for community. Regards, Manoj

…

On Thu, Oct 14, 2021, 10:54 AM Suresh Raju ***@***.***> wrote: Hi, As per the manual, the values are represented in kb/s. Could you please advise which is incorrect. Do you mean calculate it by 1024 instead of 1000? rxkB/s - Total number of kilobytes received per second. txkB/s - Total number of kilobytes transmitted per second. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATVPHILJWTADLCYAP66Q563UGZSRHANCNFSM5F6RSDLQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[EasternPA]

@iamsureshraju the memory pages have the same issue. The units are off by order of magnitude. All of the charts on my memory charts show "MB" on the y-axis, but the values being charted are actually in GB. The values you are reading are in KB, not just bytes. That's why the charted values are off by 1024.