Displaying 3 results from an estimated 3 matches for "17188msec".
2017 Apr 08
2
lvm cache + qemu-kvm stops working after about 20GB of writes
...y impressive 150MB/s
4k random r/w (close to bare metal, about 20% - 30% loss). But after a
few (usually about 4 or 5) runs (always changing the filename, but not
overfilling the FS, it drops to about 10 MBs/sec.
normal/in the beginning
read : io=3073.2MB, bw=183085KB/s, *iops=45771* , runt= 17188msec
write: io=1022.1MB, bw=60940KB/s, *iops=15235* , runt= 17188msec
but then
read : io=3073.2MB, bw=183085KB/s, *iops=**2904* , runt= 17188msec
write: io=1022.1MB, bw=60940KB/s, *iops=1751* , runt= 17188msec
or even worse up to the point that it is actually the HDD that is
written to (abou...
2017 Apr 10
0
lvm cache + qemu-kvm stops working after about 20GB of writes
...random r/w (close to bare metal, about 20% - 30% loss). But after a few
> (usually about 4 or 5) runs (always changing the filename, but not
> overfilling the FS, it drops to about 10 MBs/sec.
>
> normal/in the beginning
>
> read : io=3073.2MB, bw=183085KB/s, *iops=45771* , runt= 17188msec
> write: io=1022.1MB, bw=60940KB/s, *iops=15235* , runt= 17188msec
>
> but then
>
> read : io=3073.2MB, bw=183085KB/s, *iops=**2904* , runt= 17188msec
> write: io=1022.1MB, bw=60940KB/s, *iops=1751* , runt= 17188msec
>
> or even worse up to the point that it is actually...
2017 Apr 20
2
lvm cache + qemu-kvm stops working after about 20GB of writes
...e to bare metal, about 20% - 30% loss).
> But after a few (usually about 4 or 5) runs (always changing the
> filename, but not overfilling the FS, it drops to about 10 MBs/sec.
>
> normal/in the beginning
>
> read : io=3073.2MB, bw=183085KB/s, *iops=45771* , runt= 17188msec
> write: io=1022.1MB, bw=60940KB/s, *iops=15235* , runt= 17188msec
>
> but then
>
> read : io=3073.2MB, bw=183085KB/s, *iops=**2904* , runt= 17188msec
> write: io=1022.1MB, bw=60940KB/s, *iops=1751* , runt= 17188msec
>
> or even worse up to the point...