VK Cloud logo

How to test network performance

The network interface performance metrics depend on the availability zone in which the interacting VMs are located. Therefore, you need to compare network performance parameters first between VMs within the same zone, and then between VMs in different zones.

The iPerf utility will be used for testing, and three VMs will be created:

  • the main test VM — client;
  • an additional VM in the same availability zone as the test VM — server;
  • an additional VM in another availability zone — another server.

Preparatory steps

  1. If you have not done so already, contact technical support or your VK Cloud account manager with a request to allocate the required resources for testing.

    Wait for confirmation that the resources you need have been allocated.

  2. Make sure that SDN Sprut is connected for your project. Otherwise, contact technical support with a connection request.

  3. Create a test virtual machine with the following parameters:

    • Virtual machine category: select a category depending on the type of resource requested, or All current virtual machine types.

    • Virtual machine type: select STD-3 (Ice Lake) 4 vcpu, 16 Gb RAM from the list, or the type specified when requesting the resource.

    • Disk type: SSD is selected by default. To get maximum performance values, select the High-IOPS or Low Latency NVMe type.

    • Disk size: 256 GB is selected by default. To get maximum performance values, it is recommended to select 1500 GB, provided that High-IOPS or Low Latency NVME is selected in the Disk type field. For more information, see the section on disk performance.

    • Operating system: select Ubuntu 22.04 LTS.

    • At the Configuration step, in the Network field, select the existing SDN Sprut or create a new network with the Sprut type.

    Leave the remaining parameters at your discretion.

  4. Connect to the created VM and install all available updates. Installation methods depend on the selected OS.

1. Create the additional VMs

When testing cross-network interaction, the additional virtual machines act as servers.

  1. Create a virtual machine with the following parameters:

    • Availability zone: select the same availability zone as that of the main test VM.
    • Network: select the same SDN Sprut as that of the main test VM.

    Set the remaining parameters the same as those of the main test VM.

  2. Create another virtual machine with the following parameters:

    • Availability zone: select a different availability zone from that of the main test VM.
    • Network: select the same SDN Sprut as that of the main test VM.

    Set the remaining parameters the same as those of the main test VM.

  3. Connect to the additional VMs.

2. Determine the IP addresses of all VMs

  1. Go to the VK Cloud management console.
  2. In the Cloud Computing → Virtual Machines section, click the name of the desired VM.
  3. On the VM page, go to the Networks tab.
  4. Write down the IP addresses of the main test VM and the additional VMs. You will need them later.

3. Prepare the VMs for testing

  1. Install the iPerf utility on the test and additional virtual machines using the command:

    sudo apt install iperf3
  2. On the additional VMs, run the command to start the iPerf server part:

    iperf3 -s

4. Perform single-thread cross-network testing

You can test single-thread cross-network interaction using the ready-made iperf3_single script from VK Cloud.

  1. Test the interaction within a single zone. To do this, run the iperf3_single script on the test VM, replacing the following parameters in the script code:

    • <RESULT_OUTPUT_FILE_NAME> — the name of the file for saving the test result, for example test_collection_output_single1 for a single-thread run within a single zone. By default, the file is saved in the directory where the script is run.
    • <TEST_VM_IP> — the IP address of the test VM on which the script is run.
    • <SERVER_VM_IP> — the IP address of the additional VM (in the same zone) acting as the server.
  2. Test the interaction between different zones. To do this, run the iperf3_single script on the test VM, replacing the following parameters in the script code:

    • <RESULT_OUTPUT_FILE_NAME> — the name of the file for saving the test result, for example test_collection_output_single2 for a single-thread run between different zones. By default, the file is saved in the directory where the script is run.
    • <SERVER_VM_IP> — the IP address of the additional VM (in another zone) acting as the server.

5. Perform multi-thread cross-network testing

You can test multi-thread cross-network interaction using the ready-made iperf3_multi script from VK Cloud.

  1. Test the interaction within a single zone. To do this, run the iperf3_multi script on the test VM, replacing the following parameters in the script code:

    • <RESULT_OUTPUT_FILE_NAME> — the name of the file for saving the test result, for example test_collection_output_multi1 for a multi-thread run within a single zone. By default, the file is saved in the directory where the script is run.
    • <TEST_VM_IP> — the IP address of the test VM on which the script is run.
    • <SERVER_VM_IP> — the IP address of the additional VM (in the same zone) acting as the server.
  2. Test the multi-thread interaction between different zones. To do this, run the iperf3_multi script on the test VM, replacing the following parameters in the script code:

    • <RESULT_OUTPUT_FILE_NAME> — the name of the file for saving the test result, for example test_collection_output_multi2 for a multi-thread run between different zones. By default, the file is saved in the directory where the script is run.
    • <SERVER_VM_IP> — the IP address of the additional VM (in another zone) acting as the server.

6. Record the test results

Enter the obtained results into the spreadsheet and compare the data transfer rate (the Bitrate (Gbit/s) parameter) between two VMs in the same zone and in different zones.

Now you can compare this data with the performance of other cloud platforms.

Delete unused resources

The created resources are billed. If you no longer need them, delete them:

  1. Delete the test and additional VMs.
  2. Delete the subnets and networks in which the VMs were hosted.
Was this article helpful?