91yun a key test server package introduced
A key package is mainly to let you quickly have a basic understanding of the status of the server. Taking into account the export of network heavenly, so this package is more biased towards a key test of the network.
The main impact of the test is time-consuming to download, the entire test is run if the full bandwidth of 100M, it should be 20 minutes to 30 minutes. But if only a few hundred k download speed, then it would consume a long time, so if we see the test card in the download test, I hope you be patient.
The test results exist test91yun.log current directory. You can use vim or cat look, but also generate html pages, to facilitate access and sharing. Styles specific reference to the following html page.
Instructions:
Normal mode:
wget -N --no-check-certificate https://raw.githubusercontent.com/91yun/91yuntest/master/test_91yun.sh && bash test_91yun.sh
Test regular content that is before the normal mode. Please refer to the test output: Normal mode reference results style
Simple mode:
wget -N --no-check-certificate https://raw.githubusercontent.com/91yun/91yuntest/master/test_91yun.sh && bash test_91yun.sh s
Simple test modes include: conventional detection system parameters, bandwidth test, IO testing and national ping test. Please refer to the test output: Simple style reference model results
Mainly due to the normal mode download the test and test some routing consuming, and sometimes you may only need to quickly get the parameters of this server bandwidth, io and the delay is. So simple mode can save a lot of time. If you need further information you can use the normal mode.
Compared to the normal mode, that is, the last command to add a parameter s: bash test_91yun.sh s
Full mode:
wget -N --no-check-certificate https://raw.githubusercontent.com/91yun/91yuntest/master/test_91yun.sh && bash test_91yun.sh a
Full mode compared to the more common mode test, the test output unixbench please refer to: completely style reference model results
Compared to the normal mode, that is, the last command to add a parameter: bash test_91yun.sh a
Because unixbench test is extremely resource intensive (cpu and io will be a long time in full state), some IDC disable, or kill the process will determine abuse. Please test carefully.
In addition unixbench testing is extremely time-consuming, suggest that you run under the screen, screen to use please refer to: " Tutorial: Beginners will learn to play machine linux command: screen tutorial / screen command Detailed "
Project address: https: //github.com/91yun/91yuntest