Turn from 51Testing
http://bbs.51testing.com/viewthread.php?tid=116526
Often see a lot of people talk about LoadRunner to Linux/aix performance monitoring too little, indeed, LR for non-Windows platform monitoring is too little, but we can use IBM's Nmon for performance analysis, this is a great tool, on the official website of IBM:
Http://www-941.haw.ibm.com/collaboration/wiki/display/Wikiptype/nmon
Nmon Analysis Tools:
Http://www-941.haw.ibm.com/collaboration/wiki/display/Wikiptype/nmonanalyser
Note: Nmon is currently only available for AIX and Linux versions, not supported for HP UNIX and Solaris.
In fact, performance testing is not limited to a certain tool, LoadRunner main function is load generation, in the actual work we can rely on a number of performance analysis tools to perform performance monitoring and analysis, using the Oracle/db2/sql and other trace tools, The Perfmon,java of Windows Jprofile,nmon .... And each UNIX system comes with performance monitoring commands such as Vmstat,iostat,sar.
For performance testing, the most important thing is to understand the principle, more attention to some performance optimization methods, so for performance testing and analysis has greatly improved and help.
This is my nmon. How to use (Windy Personal Summary, if reproduced please specify)
Nmon currently supports AIX and Linux and can be downloaded to the following address for free: Http://www-941.haw.ibm.com/collaboration/wiki/display/WikiPtype/nmon
The use of Nmon is relatively simple, do not install, the corresponding version of the installation package directly on the server to a directory, run, for example:
#./nmon_x86_rhel4
The display CPU can press C, similarly, memory-m,network I/o----N, Disk I/o---D is as follows:
Press the Q key to exit Nmon, but at this point the locator is a bit messy, preferably clear.
#./nmon–f-s 30–c 100
Description:-F is output as a file, the default output is machine name + date. Nmon format, you can also use-f to specify the file name of the output, for example: #./nmon_x86_rhel4–f test.nmon-s 30–c 100;
-S is the sampling frequency, how often collect once, here I specify is 30 seconds once;
-C is the number of samples, how many times to collect, here I specify 100 times.
Note: The maximum size of a file collected here cannot exceed 65K (the limit in Excel), which is about 330 times the value of –c in Nmon.
./nmon-f-S 10-c 150
Nmon generated files larger, it is recommended not to collect too many times per collection, if you need to collect a long time of data, it is recommended to separate collection, that is, to generate multiple files, Linux can be built in multiple jobs, such as:
First create a script, for example named Nmon.sh, as follows:
#! /bin/sh
./nmon_x86_rhel4-f 6326081116_6am.nmon-s 60-c 240
To authorize this file:
#chmod 777 nmon.sh
Then build a job:
# at–f nmon.sh 6:00pm January 16
The operation is complete as follows:
If you want to build a long-term task can be done with the crontab command, it is recommended not to use this command, otherwise it is easy to forget how many tasks you built, causing background transactions to consume resources.
Analysis:
Convert the generated. nmon file to a. csv file that Excel recognizes, as follows:
# sort Test.nmon > Test.csv
The generated. csv file can then be analyzed under the Windows platform.
In general, I do not recommend Nmon monitoring for stability testing, because it is necessary to collect too much information to generate large files, in fact, to monitor the performance of Linux/unix server resources, with Vmstat and iostat These two commands to collect enough.
In/home/software/nmon
nmon.sh 10 1
10 refers to statistics every 10 seconds, 1 refers to a total of 1 minutes, every 300 times will be reborn into a file
nmon--very good Linux/aix performance counter monitoring and analysis tool