ID 435249 - Status Bar disk read speeds are incorrect on NVMe drives

Problem summary
Status Bar disk read speeds are incorrect on NVMe drives

This only seems to affect CentOS, Windows did not have the issue.

Unable to test on macOS due to hardware limitations.

Customer reported version
nuke.12.1v1

Customer reported platform
centos7

Steps to reproduce

1) Open a terminal session and run:

iostat -m -c 1 -d

This is a constantly updating disk read speed value to compare against

2) Launch Nuke or Nuke Studio

3) Read in some footage from a locally attached NVMe drive (tests were done with 16 bit Zip-1 UHD .exr files)

4) Play the footage back, and compare the read speed in the status bar between Nuke and the terminal, Nuke's numbers are consistently 2-3 times larger.

*Due to the setup on the test machine, the drive appears in isostat twice, but that is due to drive mapping and not physical hardware usage

Expected behaviour
For the numbers to be about the same, as they are on SSD's and mechanical drives

Actual behaviour
Nuke's disk speeds are consistently 2-3 times larger than what the OS says

Reproduced by support
This bug has been reproduced in:

Nuke Studio 12.1v2 - CentOS 7

Nuke Studio 12.0v1 - CentOS 7

Nuke Studio 11.0v1 - CentOS 7

Nuke Studio 10.0v1 - CentOS 7

Unable to reproduce bug in:
Nuke Studio 12.1v2 - Windows 10* when comparing Nuke's disk read to task manager, the values were consistent

Earliest version tested
Nuke Studio 10.0v1 - This issue appears to be in all versions of the product