Use the dd command to test the disk write performance

1. ddif/dev/zerooftestbs64kcount16k is not accurate because the data is not actually written to the disk at the end of the command. ddif/dev/zerooftestbs64kcount16kconvfsync is accurate, and data has been written to disk 3.dd

1. dd if =/dev/zero of = test bs = 64 k count = 16 k

This is not accurate because the data is not actually written to the disk at the end of the command.

2. dd if =/dev/zero of = test bs = 64 k count = 16 k conv = fsync

This is fairly accurate. The data has been written to the disk.

3. dd if =/dev/zero of = test bs = 64 k count = 4 k oflag = dsync

This can be regarded as a simulation of database insert operations, so it is very slow

Next let's take a look at the disk performance of the buyvm.

Dd if =/dev/zero of = test bs = 64 k count = 16 k

1073741824 bytes (1.1 GB) copied, 2.99687 seconds, 358 MB/s

The result of the first method seems to be very fast.

Dd if =/dev/zero of = test bs = 64 k count = 16 k conv = fsync

1073741824 bytes (1.1 GB) copied, 13.9241 seconds, 77.1 MB/s

This time it is much slower, so this data is of reference value.

Dd if =/dev/zero of = test bs = 64 k count = 2 k oflag = dsync

134217728 bytes (134 MB) copied, 177.813 seconds, 755 kB/s

This is the real strength of the buyvm. I tested 20 Mb/s in 84 vps.