This topic describes how to use the fio tool to test the throughput and input/output operations per second (IOPS) of an Apsara File Storage NAS (NAS) file system in Linux and Windows.
Prerequisites
A file system is created and mounted on one or more Elastic Compute Service (ECS) instances. For more information, see Get started with NAS.
Background information
The performance results in this topic are obtained from tests that are performed on Linux and Windows ECS instances by using the fio tool. These results are used as performance references for NAS file systems. To meet the performance metrics that are provided on the product page of NAS, we recommend that you use multiple ECS instances to conduct performance tests. For more information about the performance metrics, visit the product page of NAS.
If you have any feedback or questions, contact NAS technical support by clicking the button below.
Precautions
Before you conduct performance tests, take note of the following items:
The maximum throughput cannot exceed the internal bandwidth of ECS instances. If the internal bandwidth is low, the throughput is limited.
For example, you have purchased a Capacity NAS file system with the lowest capacity and its initial read bandwidth is 150 MB/s. If the internal bandwidth of your ECS instances is 100 Mbit/s, the maximum throughput can reach 12.5 MB/s. To enable the throughput to reach 150 MB/s, you need at least 12 ECS instances for testing. If the internal bandwidth of your ECS instances is 1 Gbit/s, the maximum throughput can reach 125 MB/s. To enable the throughput to reach 150 MB/s, you need at least two ECS instances for testing.
By default, a maximum of 2 concurrent Network File System (NFS) requests can be sent from a Linux-based NFS client. This limits the performance of the NFS client. After you install an NFS client, change the maximum number of concurrent NFS requests to improve the performance of the NFS client. For more information, see How do I change the maximum number of concurrent NFS requests from an NFS client?
Window NFS clients can process requests from only one file system at a time. As a result, the test performance of an NFS file system in Windows may be inaccurate. We recommend that you modify the
-numjobsparameter to increase the number of files that can be tested by the fio tool.
Procedure
Connect to the ECS instance. For more information, see Connection methods.
Install the fio tool. If the fio tool is installed, skip this step and run the performance test commands.
Linux
Operating system
Installation command
CentOS
sudo yum install fioRedhat
Alibaba Cloud Linux
Ubuntu
Run the following commands in sequence:
sudo apt-get updatesudo apt-get install fio
Debian
Windows
Download the installation package in MSI format. To download the fio installation package, visit the fio official website.
Run the performance test commands. For more information about the commands, see the following sections:
Performance test commands for Linux
This section uses a General-purpose NAS file system as an example. Run the following commands on a Linux ECS instance to test the performance.
Command used to test the random read IOPS:
fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=4K -size=1G -time_based -runtime=60 -name=Fio -directory=/mntSample test result:
Command used to test the random write IOPS:
fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=4K -size=1G -time_based -runtime=60 -name=Fio -directory=/mntSample test result:
Command used to test the random read throughput:
fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randread -bs=1M -size=1G -time_based -runtime=60 -name=Fio -directory=/mntSample test result:
Command used to test the random write throughput:
fio -numjobs=1 -iodepth=128 -direct=1 -ioengine=libaio -sync=1 -rw=randwrite -bs=1M -size=1G -time_based -runtime=60 -name=Fio -directory=/mntSample test result:
Performance test commands for Windows
In this example, a Capacity NAS file system is mounted on Disk Z and the fio tool is installed in the C:\Program Files\fio\fio.exe directory. Run the following commands to conduct performance tests.
Window NFS clients can process requests from only one file system at a time. As a result, the test performance of an NFS file system in Windows may be inaccurate. We recommend that you modify the -numjobs parameter to increase the number of files that can be tested by the fio tool.
Command used to test the random read IOPS:
"c:\Program Files\fio\fio.exe" -name=Fio -numjobs=2 -iodepth=128 -direct=1 -ioengine=windowsaio -sync=1 -rw=randread -bs=4K -size=1G -time_based -runtime=60 -group_reporting -thread -directory=Z\:\Sample test result:
Command used to test the random write IOPS:
"c:\Program Files\fio\fio.exe" -name=Fio -numjobs=2 -iodepth=128 -direct=1 -ioengine=windowsaio -sync=1 -rw=randwrite -bs=4K -size=1G -time_based -runtime=60 -group_reporting -thread -directory=Z\:\Sample test result:
Command used to test the random read throughput:
"c:\Program Files\fio\fio.exe" -name=Fio -numjobs=2 -iodepth=128 -direct=1 -ioengine=windowsaio -sync=1 -rw=randread -bs=1M -size=1G -time_based -runtime=60 -group_reporting -thread -directory=Z\:\Sample test result:
Command used to test the random write throughput:
"c:\Program Files\fio\fio.exe" -name=Fio -numjobs=2 -iodepth=128 -direct=1 -ioengine=windowsaio -sync=1 -rw=randwrite -bs=1M -size=1G -time_based -runtime=60 -group_reporting -thread -directory=Z\:\Sample test result:
fio parameters
The following table describes the parameters in the preceding fio commands.
Parameter | Description |
direct | Specifies whether to use direct I/O. Default value: 1. Valid values:
|
iodepth | The I/O queue depth during the test. For example, |
rw | The read/write policy that is used during the test. Valid values:
|
ioengine | The I/O engine that fio uses for the test. In most cases, libaio is used. For information about other available I/O engines, see the fio documentation. |
bs | The block size of I/O units. Values for reads and writes can be specified in the <Value for reads>,<value for writes> format. If you do not specify a value, the default value is used. |
size | The size of the test files. fio ends the test only after the specified size of the files is read or written, unless limited by specific factors, such as runtime. If this parameter is not specified, fio uses the size of all given files or devices. The valid values can also be a percent that ranges from 1% to 100%. For example, if the size parameter is set to 20%, fio uses 20% of the size of all given files or devices. |
numjobs | The number of concurrent threads that are used during the test. |
runtime | The duration of the test, which indicates the period of time for which fio runs. If this parameter is not specified, the test does not end until the files whose size is specified by the size parameter are read or written in the block size specified by the bs parameter. |
group_reporting | The display mode of the test results. If this parameter is specified, per-process statistics instead of per-task statistics are displayed. |
directory | The mount path of the file system to be tested. |
name | The name of the test. You can specify the parameter based on your needs. |
For more information about the parameters, see fio(1) - Linux man page.
FAQ
How do I increase the read and write throughput threshold of a General-purpose NAS file system?
Why does a file system give a slow response or does not respond when I run the ls command?
How do I improve the NFS sequential read performance on Linux kernel 5.4 or later?
For more information about NAS performance, see FAQ about the performance of NAS file systems.