First, install the rstatd daemon on the server
Installation steps:
1. download rstatd from the Internet
2. Place the file in the /home/user directory
3. chmod 777 RPC.RSTATD---- Change the Read and write permissions of the file, with all permissions.
4. chmod 777 Configure--- ibid .
5../configure--- configuration
6. Make--- compile
7. Make Install--- installation
8. RPC.RSTATD--- start the rstatd process
Second, configure in LR
Add measurementfrom LR , fill in the IPof the Linux machine , appear all unix/linux counters, including CPU ,mem ,disk ,thenetwork . Introduction to several commonly used:
average load: in the last 1 minutes, the average load
CPU UTILIZATION:CPU Utilization
disk Traffic:disk transfer rate
Paging Rate: The number of memory pages per second read from disk to physical memory, or from physical memory to the paging file
swap-in Rate: number of processes swapped to memory per second
swap-out Rate: processes that are swapped out of memory per second
to supplement some common problems and treatment methods:
1. A " denied permission " prompt appears during theexecution of configuration or installation commands ;
A: Due to file permissions, the current user should be given the "777" permission of all Files , that is, Full Control permissions.
2, installed after the LoadRunner from the information, but no error;
A : It may be that the returned information value is small, so it is almost invisible in the diagram, for example: If the program is not running, theCPU usage is close to 0, so there is no change in the monitor diagram. It is also possible that the sampling frequency is too large, can be set in the chart 1 seconds to obtain information, so that the interface is refreshed more timely.
3, monitoring a period of time after the loadrunner Prompt error occurred can not continue to monitor the information;
A : It may be because the CPU is in a high-load state for a long time, which causes the system to automatically shut down the service. You can Avoid this situation by re-adding the counter in LoadRunner and setting the sampling time a little longer.
4, before with LoadRunner monitoring are successful, but again monitoring not information;
A: It is possible that the rstatd Daemon was not opened because of a system reboot . You can manually reopen it, use the command "RPC.RSTATD", and use the "rpcinfo-p" command to see if the current system has started RSTATD daemon process.
This article is from the "Cockroach Software Testing" blog, please be sure to keep this source http://xqtesting.blog.51cto.com/4626073/1538123