Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk speed half of what they really are #489

Open
stayprivates opened this issue Dec 4, 2018 · 7 comments
Open

Disk speed half of what they really are #489

stayprivates opened this issue Dec 4, 2018 · 7 comments

Comments

@stayprivates
Copy link

Hello,

Ubuntu 18.04 X64, shell 3.28. The numbers show for disk transfer speed are about half of what iotop and Nautilus are showing. The laters have the same numbers.

Thanks.

@maruncz
Copy link

maruncz commented Jan 12, 2019

Hi, same here, same system and shell

@nouspiro
Copy link

nouspiro commented Feb 2, 2019

Same here.

@Tomaskom-cz
Copy link

I also have this issue, both on OpenSUSE Leap 15.0 (Gnome 3.26.2) and OpenSUSE Tumbleweed (Gnome 3.32.2). When comparing to iotop and copy dialog, the speed seems always to be half of the real read and write. Shows the same wrong value in the tooltip and the open dialog.

One of the machines I tested this on has just one physical hard drive, the other has two, this has no effect.

Screenshot from 2019-05-27 23-03-02

@romanstingler
Copy link

does it change the behavior if you set the refresh time to 1000ms?

@nouspiro
Copy link

Yeah same behavior even with refresh rate set to 1000ms.

@JuniorPolegato
Copy link

Hi!
I got the solution: JuniorPolegato@07540c6

JuniorPolegato added a commit to JuniorPolegato/gnome-shell-system-monitor-applet that referenced this issue Dec 5, 2021
Issue: paradoxxxzero#489
The original code was accumulating sectors of disks/block devices and partitions, duplicating the read and write sectors counting.
Now the code gets the block device list and just accumulates their sectors.
I found a division of these sectors (512 bytes each) by 1024 and 8 (8192 => 8k) to get MiB, but that's not right, it is needed to divide by 2k (or *512/1024/1024) not 8k, maybe due to the accumulation of block devices and partitions, however, when operating on one partition (dd if=/dev/sda1 of=/dev/null bs=4k), it duplicates the accumulated sectors, so you need to divide by 4k, not 8k, getting half the speed. But if you are operating directly on a disk device (dd if=/dev/sda of=/dev/null bs=4k), does not duplicate the accumulated sectors, so you need to divide by 2k, not 8k, getting half of half the speed.
Nowadays, disk space is in MB, not in MiB, so I adjusted this too.
JuniorPolegato added a commit to JuniorPolegato/gnome-shell-system-monitor-applet that referenced this issue Dec 5, 2021
Issue: paradoxxxzero#489
The original code was accumulating sectors of disks/block devices and partitions, duplicating the read and write sectors counting.
Now the code gets the block device list and just accumulates their sectors.
I found a division of these sectors (512 bytes each) by 1024 and 8 (8192 => 8k) to get MiB, but that's not right, it is needed to divide by 2k (or *512/1024/1024) not 8k, maybe due to the accumulation of block devices and partitions, however, when operating on one partition (dd if=/dev/sda1 of=/dev/null bs=4k), it duplicates the accumulated sectors, so you need to divide by 4k, not 8k, getting half the speed. But if you are operating directly on a disk device (dd if=/dev/sda of=/dev/null bs=4k), does not duplicate the accumulated sectors, so you need to divide by 2k, not 8k, getting half of half the speed.
Nowadays, disk space is in MB, not in MiB, so I adjusted this too.
@dr-br
Copy link

dr-br commented Oct 17, 2023

Error still persistent:
Bildschirmfoto_vom_2023-10-17_10-33-50

Gnome version: 44.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants