VK Cloud logo

Block Storage Disk Performance

The VK Cloud data storage system uses disks of various types:

  • HDD;
  • SSD;
  • High-IOPS SSD;
  • High-IOPS HA SSD;
  • Low Latency NVMe.

For more information, see the section on block storage disks in VK Cloud.

Each disk type is guaranteed certain performance characteristics. Quotas and limits on the number and size of disks are provided in the article Quotas and limits.

Disk type
(API name)

Read, IOPS
min.—max.

Read,
IOPS/GB

Write, IOPS
min.—max.

Write,
IOPS/GB

Latency, ms
max.

Network HDD disk
(ceph-hdd)

300–2400

1

150–800

1

20

Network SSD disk
(ceph-ssd)

1000–16000

30

500–8000

15

3

High-IOPS SSD
(high-iops)

10000–45000

30

5000–30000

25

1

High-IOPS HA SSD
(high-iops-ha)

7500–35000

25

2000–12000

15

1

Low Latency NVMe
(ef-nvme)

10000–75000

75

5000–50000

35

0.5

Network HDD disk

Below are detailed performance characteristics for network HDD disks of different volumes.

Size, GB

Read, IOPS
bs=4k,
iodepth=32

Read, MB/s
bs=1M,
iodepth=16

Write, IOPS
bs=4k,
iodepth=32

Write, MB/s
bs=1M,
iodepth=16

10

300

38

150

19

50

300

38

150

19

100

300

38

150

19

250

300

38

250

31

500

500

63

500

63

1000

1000

125

800

100

1500

1500

188

800

100

2000

2000

250

800

100

Here bs and iodepth are the performance testing parameters.

Network SSD disk

Below are detailed performance characteristics for network SDD disks of different volumes.

Size, GB

Read, IOPS
bs=4k,
iodepth=32

Read, MB/s
bs=1M,
iodepth=16

Write, IOPS
bs=4k,
iodepth=32

Write, MB/s
bs=1M,
iodepth=16

10

1000

125

500

63

50

1500

188

750

94

100

3000

375

1500

188

250

7500

400

3750

400

500

15000

400

7500

400

1000

16000

400

8000

400

1500

16000

400

8000

400

2000

16000

400

8000

400

Here bs and iodepth are the performance testing parameters.

High-IOPS SSD

Below are detailed performance characteristics for network High-IOPS SSD disks of different volumes.

Size, GB

Read, IOPS
bs=4k,
iodepth=32

Read, MB/s
bs=1M,
iodepth=16

Write, IOPS
bs=4k,
iodepth=32

Write, MB/s
bs=1M,
iodepth=16

10

10000

500

5000

500

50

10000

500

5000

500

100

10000

500

5000

500

250

10000

500

6250

500

500

15000

500

12500

500

1000

30000

500

25000

500

1500

45000

500

30000

500

2000

45000

500

30000

500

Here bs and iodepth are the performance testing parameters.

High-IOPS HA SSD

Below are detailed performance characteristics for network High-IOPS HA SSD disks of different volumes.

Size, GB

Read, IOPS
bs=4k,
iodepth=32

Read, MB/s
bs=1M,
iodepth=16

Write, IOPS
bs=4k,
iodepth=32

Write, MB/s
bs=1M,
iodepth=16

10

7500

375

2000

250

50

7500

375

2000

250

100

7500

375

2000

250

250

7500

375

3750

300

500

12500

375

7500

300

1000

25000

375

12000

300

1500

35000

375

12000

300

2000

35000

375

12000

300

Here bs and iodepth are the performance testing parameters.

Low Latency NVMe

Below are detailed performance characteristics for local Low Latency NVMe disks of different volumes.

Size, GB

Read, IOPS
bs=4k,
iodepth=32

Read, MB/s
bs=1M,
iodepth=16

Write, IOPS
bs=4k,
iodepth=32

Write, MB/s
bs=1M,
iodepth=16

10

10000

500

5000

500

50

10000

500

5000

500

100

10000

500

5000

500

250

18750

586

8750

500

500

37500

1172

17500

547

1000

75000

1200

35000

900

1500

75000

1200

50000

900

2000

75000

1200

50000

900

Here bs and iodepth are the performance testing parameters.

Disk performance testing

  1. Before testing, make sure that the following conditions are met:

    • the disk is non-bootable;
    • there is no load on the disk from the operating system.

    If these conditions are met, the IOPS measurement results should match the following values:

    Test type

    Result, IOPS

    Read and write with 4 KB blocks in 32 threads

    Matches the SLA

    Read and write with 8 KB blocks in 32 threads

    At least 75% of the SLA

    Read and write with 16 KB blocks in 32 threads

    At least 50% of the SLA

  2. Test the disk.

    To measure IOPS for reading and writing, use the DiskSpd or FIO utilities.

    DiskSpd

    1. Run the command prompt as administrator.

    2. Create a temp directory and an empty file of at least 10 GB:

      md C:\tempfsutil file createnew C:\temp\test.bin 10485760000
    3. Download the utility and extract it to the desired directory.

    4. Navigate to the amd64 directory of the extracted utility.

    5. Run the diskspd command with parameters corresponding to the test type:

      • -w — percentage of write operations, -w0 for a read test, -w100 for a write test;
      • -b — block size in bytes.

      For a detailed description of all diskspd command parameters, see the official documentation.

      • Random write test with 4 KB blocks:

        diskspd -Suw -b4K -o1 -t32 -r -w100 C:\temp\test.bin > C:\temp\random_write_results.txt
      • Random read test with 4 KB blocks:

        diskspd -Suw -b4K -o1 -t32 -r -w0 C:\temp\test.bin > C:\temp\random_read_results.txt

    FIO

    1. Download and install FIO.

    2. Run the fio command with parameters corresponding to the test type:

      • --rw — randread or randwrite.
      • --bs — block size.
      • --filename — name of the test file.
      • --rate_iops — target IOPS value (optional). Use this parameter to obtain a more accurate latency value when testing the target IOPS value.

      For a detailed description of all command parameters, see the FIO documentation.

      • Random write test with 4 KB blocks:

        fio `   --name=randwrite `   --iodepth=32 `   --rw=randwrite `   --bs=4k `   --direct=1 `   --size=10G `   --numjobs=1 `   --runtime=240 `   --group_reporting `   --filename=C:\Users\ADMIN\test
      • Random read test with 4 KB blocks:

        fio `   --name=randread `   --iodepth=32 `   --rw=randread `   --bs=4k `   --direct=1 `   --size=10G `   --numjobs=1 `   --runtime=240 `   --group_reporting `   --filename=C:\Users\ADMIN\test
  3. If, after meeting all the conditions, the test results do not match the specified values, contact technical support.

  4. After testing is completed and the results are processed, delete the large test files to free up disk space. Quotas and limits on the use of VK Cloud resources are provided in the article Quotas and limits.

Was this article helpful?