06-11-2020, 08:47 AM
@sohamb03
I'm afraid you'll have to repeat all the storage benchmarking section!!
Why?!.. you may ask!... Simply --and correct me if I'm work-- because you were benchmarking inside the /tmp folder, which is a loop-mounted folder (as /dev/loop0). Thus the rates you got ain't really those of your virtual disk (/dev/vda), but just a loop-mounted folder/device.
Those, who did have OVZ editions of VPS-9 will be familiar with the 600/700 MB/s sequential write... But shouldn't be the case for KVM editions.
As to why your storage device
If you happened to be used the virtio_scsi version, your virtual disk would have the 'S' prefix instead of 'V'. But it's the deploy-er decision not ours.
Anyway, I think you're onto something here, and I'll comment further one you update the miss-hap.
I'm afraid you'll have to repeat all the storage benchmarking section!!
(06-11-2020, 07:27 AM)sohamb03 Wrote:STORAGE BENCHMARK
I've 70GB of storage on my VPS. In VPS 9, you can choose in multiples of 5, and I didn't need much storage till now, but I'll need more soon with another OS re-installation.
Code: (Select All)Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 64M 3.8G 2% /dev/shm
tmpfs 3.9G 352M 3.5G 9% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/mapper/centos-root 47G 17G 30G 36% /
/dev/loop0 1.5G 9.0M 1.4G 1% /tmp
/dev/mapper/centos-home 23G 1.1G 22G 5% /home
/dev/vda1 1014M 228M 787M 23% /boot
tmpfs 783M 4.0K 783M 1% /run/user/0
tmpfs 783M 0 783M 0% /run/user/5003
For the boot time: (Actually I've a GUI - XFCE - running on the VPS; not sure why it didn't show up )
Code: (Select All)Startup finished in 861ms (kernel) + 2.761s (initrd) + 12.130s (userspace) = 15.753s
Although, the boot time is pretty cool.
Now for the tests, directly from the Benchmarking Script:
Code: (Select All)Disk Speed
----------
I/O (1st run) : 799 MB/s
I/O (2nd run) : 781 MB/s
I/O (3rd run) : 827 MB/s
Average I/O : 802.333 MB/s
Which is a remarkable performance!
This is the disk-speed-beta.sh script, not yet merged into the benchmarking script but just a confirmation of the above results plus the cached mode.
Code: (Select All)Testing hard drive write speed.
Pass 1... Pass 2... Pass 3... 693 MB/s
Testing hard drive read speed with caching.
Pass 1... Pass 2... Pass 3... 2.5 GB/s
Testing hard drive read speed without caching.
Pass 1... Pass 2... Pass 3... 859 MB/s
(PS: Here I encountered a strange problem. I'm not an expert at all this; since I don't deal with hardware at all. For some reason, my system seems to be missing "/dev/sda" and I've the least idea why, so I performed the upcoming tests on "/dev/loop0". No idea if that makes a difference but nevermind. If I were to make a wild guess, I got CentOS 7 installed from ISO since I needed the default partitions for some purpose ... maybe that's why.)
HDPARM
Direct:
Code: (Select All)/dev/loop0:
Timing O_DIRECT cached reads: 2936 MB in 1.99 seconds = 1472.22 MB/sec
Timing O_DIRECT disk reads: 1500 MB in 0.91 seconds = 1648.67 MB/sec
/dev/loop0:
Timing O_DIRECT cached reads: 2814 MB in 1.99 seconds = 1411.65 MB/sec
Timing O_DIRECT disk reads: 1500 MB in 1.23 seconds = 1219.07 MB/sec
/dev/loop0:
Timing O_DIRECT cached reads: 3208 MB in 1.99 seconds = 1608.77 MB/sec
Timing O_DIRECT disk reads: 1500 MB in 0.93 seconds = 1604.51 MB/sec
Cached:
Code: (Select All)/dev/loop0:
Timing cached reads: 6810 MB in 1.98 seconds = 3439.02 MB/sec
Timing buffered disk reads: 1426 MB in 3.00 seconds = 475.09 MB/sec
/dev/loop0:
Timing cached reads: 5214 MB in 1.98 seconds = 2630.66 MB/sec
Timing buffered disk reads: 1500 MB in 1.87 seconds = 800.39 MB/sec
/dev/loop0:
Timing cached reads: 6034 MB in 1.99 seconds = 3037.79 MB/sec
Timing buffered disk reads: 1500 MB in 1.70 seconds = 880.70 MB/sec
IOPING
Disk Seek Rate:
Code: (Select All)--- /dev/loop0 (block device 1.46 GiB) ioping statistics ---
3.95 k requests completed in 2.46 s, 15.4 MiB read, 1.60 k iops, 6.27 MiB/s
generated 3.95 k requests in 3.00 s, 15.4 MiB, 1.32 k iops, 5.14 MiB/s
min/avg/max/mdev = 17.2 us / 623.4 us / 59.9 ms / 1.60 ms
Disk Sequential Speed:
Code: (Select All)--- /dev/loop0 (block device 1.46 GiB) ioping statistics ---
2.33 k requests completed in 2.50 s, 583 MiB read, 934 iops, 233.7 MiB/s
generated 2.33 k requests in 3.00 s, 583.2 MiB, 777 iops, 194.4 MiB/s
min/avg/max/mdev = 245.1 us / 1.07 ms / 21.4 ms / 1.57 ms
DISK I/O LATENCY:
Default Mode:
Code: (Select All)--- /tmp (ext4 /dev/loop0) ioping statistics ---
19 requests completed in 2.31 ms, 76 KiB read, 8.22 k iops, 32.1 MiB/s
generated 20 requests in 19.0 s, 80 KiB, 1 iops, 4.21 KiB/s
min/avg/max/mdev = 86.7 us / 121.6 us / 195.3 us / 31.1 us
Asynchronous Mode:
Code: (Select All)--- /tmp (ext4 /dev/loop0) ioping statistics ---
19 requests completed in 6.32 ms, 76 KiB read, 3.00 k iops, 11.7 MiB/s
generated 20 requests in 19.0 s, 80 KiB, 1 iops, 4.21 KiB/s
min/avg/max/mdev = 103.2 us / 332.7 us / 1.80 ms / 477.6 us
Direct Mode:
Code: (Select All)--- /tmp (ext4 /dev/loop0) ioping statistics ---
19 requests completed in 7.57 ms, 76 KiB read, 2.51 k iops, 9.80 MiB/s
generated 20 requests in 19.0 s, 80 KiB, 1 iops, 4.21 KiB/s
min/avg/max/mdev = 83.0 us / 398.5 us / 2.52 ms / 645.5 us
Cached Mode:
Code: (Select All)--- /tmp (ext4 /dev/loop0) ioping statistics ---
19 requests completed in 493.8 us, 76 KiB read, 38.5 k iops, 150.3 MiB/s
generated 20 requests in 19.0 s, 80 KiB, 1 iops, 4.21 KiB/s
min/avg/max/mdev = 13.3 us / 26.0 us / 177.9 us / 35.9 us
Write Mode:
Code: (Select All)--- /tmp (ext4 /dev/loop0) ioping statistics ---
19 requests completed in 69.6 ms, 76 KiB written, 272 iops, 1.07 MiB/s
generated 20 requests in 19.0 s, 80 KiB, 1 iops, 4.21 KiB/s
min/avg/max/mdev = 1.10 ms / 3.67 ms / 20.0 ms / 4.16 ms
Alternate Read-Write Mode:
Code: (Select All)--- /tmp (ext4 /dev/loop0) ioping statistics ---
19 requests completed in 3.18 s, 76 KiB, 5 iops, 23.9 KiB/s
generated 20 requests in 21.2 s, 80 KiB, 0 iops, 3.78 KiB/s
min/avg/max/mdev = 110.9 us / 167.3 ms / 3.15 s / 704.1 ms
Why?!.. you may ask!... Simply --and correct me if I'm work-- because you were benchmarking inside the /tmp folder, which is a loop-mounted folder (as /dev/loop0). Thus the rates you got ain't really those of your virtual disk (/dev/vda), but just a loop-mounted folder/device.
Code: (Select All)
Filesystem Size Used Avail Use% Mounted on
.....
/dev/mapper/centos-root 47G 17G 30G 36% /
/dev/loop0 1.5G 9.0M 1.4G 1% /tmp
/dev/mapper/centos-home 23G 1.1G 22G 5% /home
/dev/vda1 1014M 228M 787M 23% /boot
....
Those, who did have OVZ editions of VPS-9 will be familiar with the 600/700 MB/s sequential write... But shouldn't be the case for KVM editions.
As to why your storage device
(06-11-2020, 07:27 AM)sohamb03 Wrote: (PS: Here I encountered a strange problem. I'm not an expert at all this; since I don't deal with hardware at all. For some reason, my system seems to be missing "/dev/sda" and I've the least idea why, so I performed the upcoming tests on "/dev/loop0". No idea if that makes a difference but nevermind. If I were to make a wild guess, I got CentOS 7 installed from ISO since I needed the default partitions for some purpose ... maybe that's why.)It's not a hardware issue!.. Your running in a virtual environment!.. It's a device driver issue, and it's because you're using the virtio_blk device driver; just run this command to attest for that:
Code: (Select All)
lsmod | grep virt
If you happened to be used the virtio_scsi version, your virtual disk would have the 'S' prefix instead of 'V'. But it's the deploy-er decision not ours.
Anyway, I think you're onto something here, and I'll comment further one you update the miss-hap.