1. For a server with mysql database installed, the most important resource is iops (I/O per second) and memory, so it is best to test the iops performance of the server before installing and deploying a database server. Use the sysbench test.
2.sysbench installation and use
download linkhttps://github.com/akopytov/sysbench/releases Find the corresponding version to download
Unzip the tarball:
cd sysbench
./autogen.sh
./configure
make && make install
3. Use a directory to generate a test file:
cd /data/test
sysbench --test=fileio --file-num=4 --file-block-size=8k --file-total-size=4G --file-test-mod=rndrd --file-extra-flags=direct --max-requests=0 --time=1200 --threads=4 prepare
--test=fileio ##Test the io performance of the server, you can also test the memory, cpu, etc.
--file-num=4 ##Generate 4 test files
--file-block-size=8k ##File block size, this value is best consistent with the size of the mysql database innodb_page_size
--file-total-size=4G ##4 total file size
--file-test-mod=rndrd ##Test random io read performance, random io is written as rndwr, generally only test random read and write io, sequential io performance is not tested
--file-extra-flags=direct ##Test file is written to disk, skip the cache, corresponding to the parameter innodb_flush_method=O_DIRECT in mysql, skip the first write to the file system cache, directly drop. Will affect mysql performance, but can improve data security.
--max-requests=0##Maximum number of requests, 0 means no limit
--time=1200 ##Maximum duration
--threads=4 ##Processing threads
Prepare ##Generate file, corresponding parameters and run start test, cleanup clean test file

Start the test after generating the corresponding file, using the run parameter
3. Start testing disk random read performance

--report-interval=3 Generate report information every 3 seconds
4. When running sysbench, view the disk information through iostat:

Iostat -xm 3## refreshes the information every 3 seconds. The unit of xm extended output information is m/s.
The more important value is r/s, w/s, and %util sees %util as 100. This indicates that the disk is basically full and reaches the upper performance limit.
5. View the sysbench run completion information and calculate the iops value.

In the above, the random read performance is tested, and the iops value that is important for the database can be calculated by this parameter:
4.67X1024/8(file-block-size)=597 ##Disk This is the random read performance per second, which is a relatively high value. The normal SSD disk is basically 300iops. In addition, the test time should be set to one day or two in the formal environment. The value tested in days is more accurate.
6. View the server disk scheduling algorithm:

This is directly for the deadline, no need to modify it. If noop or cfq is suggested to be changed to deadline. Modify the method echo deladline >/sys/block/xvde/queue/scheduler