Introduction and deployment guide of nmon performance monitoring tools

Introduction and deployment guide of nmon performance monitoring tools
1. Brief Introduction to nmon

Nmon is a performance monitoring tool developed by IBM for the operating system layer. It is available in two versions: aix and linux.

2. nmon2.1 and nmon for aix

Https://www.ibm.com/developerworks/community/wikis/home? Lang = en #! /Wiki/Power % 20 Systems/page/nmon

2.2 nmonfor linux

Http://nmon.sourceforge.net/pmwiki.php? N = Site. Download

3. Main Parameters

Serial number	Parameters	Brief Description
1	-F	Required for nmon, indicating to output monitoring data to a file. The default file name is hostname_yymmdd_hhmi.nmon.
2	-T	Output monitoring data of top processes
3	-T	As-t plus saves command line arguments in UARG section
4	-S	Between refreshing the screen [default 2], in seconds
5	-C	Of refreshes [default millions]

4. Automatic Monitoring deployment method 4.1: create a directory for storing nmon programs and logs

[Root @ INFA] # mkdir-p/u01/nmon/log/day

[Root @ INFA] # mkdir-p/u01/nmon/log/week

4.2 develop a crontab scheduled task (taking linux as an example) 4.2.1 deploy crontab by storing monitoring data in days

0 0 ***/u01/nmon/nmon_x86_64_rhel45-fT-m/u01/nmon/log/day-s 60-c 1440

Note:-s60: collects data every 60 seconds.

-C 1400: 1440 times of continuous collection, 1400*60 exactly for a whole day

4.2.2 deploying crontab by storing monitoring data in weeks

35 13 ** 0/u01/nmon/nmon_x86_64_rhel45-fT-m/u01/nmon/log/week-s 900-c 672

Note:-s900: collects data every 900 seconds.

-C 672: 672 times of continuous collection, 672*900 is exactly the time of 7 days

5. parsing tool nmon_analyser

After the performance indicator data collected by nmon is stored in the. nmon file, it is a plain text file with poor display effect and no graphics. You can use the nmon_analyser tool to generate a nice trend chart and format detailed data by time.

The current version is nmon Analyser V3.4 ,:

Https://www.ibm.com/developerworks/community/wikis/home? Lang = en #! /Wiki/Power % 20 Systems/page/nmon_analyser

6. Manually run nmon interactive monitoring

[Root @ INFA log] #/u01/nmon/nmon_x86_64_rhel45

Output Window:

+ Nmon-14g --------------------- Hostname = INFA --------- Refresh = 0 secs ---. 17 ------------------- + | | ------------------------------ For help type H or... | | ######### Nmon -? -Hint | | ########### Nmon-h-full | ############ | | ######### To start the same way every time | | ######### Set the NMON ksh variable | ########## | | ------------------------------ | | | Use these keys to toggle statistics on/off: | | C = CPU l = CPU Long-term-= Faster screen updates | | M = Memory j = Filesystems + = Slower screen updates | | D = Disks n = Network V = Virtual Memory | | R = Resource N = NFS v = Verbose hints | | K = kernel t = Top-processes. = only busy disks/procs | | H = more options q = Quit | | Bytes |

The focus is on the "these keys to toggle statistics on/off" section. For example, to monitor the network, enter "n ",

(1) Input n and the output result is as follows:

+ Nmon-14g --------------------- Hostname = INFA --------- Refresh =2 secs---. 48 ----------------- + | Network I/O --------------------------------------------------------------------------------- | | I/F Name Recv = KB/s Trans = KB/s packin packout insize outsize Peak-> Recv Trans | | Lo 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 | | Eth2 0.0 1.1 0.5 1.0 60.0 1080.0 4.0 8.7 | | Network Error Counters ---------------------------------------------------------------------- | | I/F Name iErrors iDrop iOverrun iFrame oErrors oDrop oOverrun oCarrier oColls | | Lo 0 0 0 0 0 0 0 0 0 | | Eth2 0 0 0 0 0 0 0 0 0 | | Bytes |

The above data is refreshed every 2 seconds.

(2) After inputting uppercase C, the output result is as follows:

X --------------------------- + ------------------------------------------------- + x XCPU User % Sys % Wait % Idle | 0 | 25 | 50 | 75 100 | x X 1 0.0 0.0 0.0 100.0 |> | x X 2 0.5 0.0 0.0 99.5 |> | x X 3 0.5 0.5 0.5 98.5 |> | x X 4 0.5 0.0 1.0 98.5 |> | x X 5 0.0 0.0 0.0 100.0 |> | x X 6 1.0 0.0 0.0 99.0 |> | x X 7 1.0 0.0 2.5 96.5 | W> | x X 8 0.5 0.0 1.0 |> | x X 9 0.5 0.0 0.0 99.5 |> | x X 10 1.5 0.0 6.0 92.5 | WWW> | x X 11 0.0 0.0 0.0 |> | x X 12 26.0 7.8 44.8 | uuuuuuuuuuuussswwwwwwwwwwwwwwwwwwwwwwwwww> | x X 13 34.5 4.1 34.5 26.9 | UUUUUUUUUUUUUUUUUssWWWWWWWWWWWWWWWWW> | x X 14 20.0 3.5 30.5 46.0 | uuuuuuuuswwwwwwwwwwwww> | x X 15 5.5 1.0 7.5 86.0 | UUWWW> | x X 16 22.2 5.1 13.1 59.6 | uuuuuuuuuusswwwwww> | x X 17 8.5 1.5 8.0 82.1 | UUUUWWW> | x X 18 8.0 1.0 9.0 82.1 | UUUWWWW> | x X 19 0.0 0.0 0.0 100.0 |> | x X 20 1.0 0.5 1.5 |> | x X 21 1.0 0.0 0.0 99.0 |> | x X 22 0.0 0.0 1.0 |> | x X 23 18.1 4.7 32.1 45.1 | uuuuuuuusswwwwwwwwwwwwww> | x X 24 0.0 0.0 0.0 100.0 |> | x X --------------------------- + ------------------------------------------------- + x XAvg 6.2 1.2 8.0 84.7 | UUUWWW> | x X --------------------------- + ------------------------------------------------- +

The above data is refreshed every 2 seconds.

Author: LI Junjie (Network Name: Step-by-Step), engaged in "system architecture, operating system, storage device, database, middleware, application" six levels of systematic performance optimization work

Join the system performance optimization professional group to discuss performance optimization technologies. GROUP: 258187244