> You'll only reach those numbers in the ideal situation. Is there just one
> program doing this disk i/o, sequentially, from a single thread?
The IO is sequential write of a stream of very large blocks of data onto a
drive that is only say 30% full. So yes you should be able to reach 120 mbytes
> Have you tried booting up Linux on the same hardware, and running the same
> tests? That would be a good way to narrow down whether the issue is hardware
> or software.
No just other Linux systems. Hardware in question is corporate system -- so
gray area as to if I can or should boot Linux .
On 2-6-2017 20:14, remmm wrote:
> These write speeds are in the range of 18 to 25 MBytes per second for
> spinning disks and about 50 Mbytes/sec for SSDs. Keep in mind these numbers
> should be more like 120 MBytes/sec for spinning disks and 300 MBytes/sec for
> SSDs.
You'll only reach thos
I'm seeing slow write speeds from both Python and C code on some Windows
workstations. In particular both Python "write" and numpy "tofile" method
suffers from this issue. I'm wondering if anyone has any ideas regarding if
this is a known issue, know the cause, or how to resolve the issue? Th
