Need guidance on VMStat

I need some guidance on the differences in observations, not sure how significantly different are they.

Also, It would be nice to hear on the values and what the obvious tuning for performance missing.

Observation 1

ending vmstat -v	              3948544 memory pages	
ending vmstat -v	              3814672 lruable pages	
ending vmstat -v	               243195 free pages	
ending vmstat -v	                    2 memory pools	
ending vmstat -v	               935117 pinned pages	
ending vmstat -v	                 80.0 maxpin percentage	
ending vmstat -v	                  3.0 minperm percentage	
ending vmstat -v	                 90.0 maxperm percentage	
ending vmstat -v	                 23.5 numperm percentage	
ending vmstat -v	               896556 file pages	
ending vmstat -v	                  0.0 compressed percentage	
ending vmstat -v	                    0 compressed pages	
ending vmstat -v	                 23.5 numclient percentage	
ending vmstat -v	                 90.0 maxclient percentage	
ending vmstat -v	               896556 client pages	
ending vmstat -v	                    0 remote pageouts scheduled	
ending vmstat -v	                  464 pending disk I/Os blocked with no pbuf	
ending vmstat -v	              1032267 paging space I/Os blocked with no psbuf	
ending vmstat -v	                 2484 filesystem I/Os blocked with no fsbuf	
ending vmstat -v	                 8944 client filesystem I/Os blocked with no fsbuf	
ending vmstat -v	                40125 external pager filesystem I/Os blocked with no fsbuf	
ending vmstat -s		
ending vmstat -s	          38982094539 total address trans. faults	
ending vmstat -s	           6100679791 page ins	
ending vmstat -s	           3108906644 page outs	


ending vmstat -s	              1528952 paging space page ins	
ending vmstat -s	             20919908 paging space page outs	
ending vmstat -s	                    0 total reclaims	
ending vmstat -s	          26582526369 zero filled pages faults	
ending vmstat -s	            109402572 executable filled pages faults	
ending vmstat -s	          14913211346 pages examined by clock	
ending vmstat -s	                21329 revolutions of the clock hand	
ending vmstat -s	           7596297938 pages freed by the clock	
ending vmstat -s	            422804303 backtracks	
ending vmstat -s	               165435 free frame waits	
ending vmstat -s	                    0 extend XPT waits	
ending vmstat -s	            171151938 pending I/O waits	
ending vmstat -s	           8362673346 start I/Os	
ending vmstat -s	            700405201 iodones	

ending vmstat -s	          80112714722 cpu context switches	
ending vmstat -s	           8015040872 device interrupts	
ending vmstat -s	           2288856795 software interrupts	
ending vmstat -s	          11017018858 decrementer interrupts	
ending vmstat -s	            181940875 mpc-sent interrupts	
ending vmstat -s	            170300031 mpc-receive interrupts	
ending vmstat -s	            697499589 phantom interrupts	
ending vmstat -s	                    0 traps	
ending vmstat -s	         311298713896 syscalls

Observation 2

vmstat -v	              3948544 memory pages	
vmstat -v	              3814672 lruable pages	
vmstat -v	               246307 free pages	
vmstat -v	                    2 memory pools	
vmstat -v	               935080 pinned pages	
vmstat -v	                 80.0 maxpin percentage	
vmstat -v	                  3.0 minperm percentage	
vmstat -v	                 90.0 maxperm percentage	
vmstat -v	                 23.4 numperm percentage	
vmstat -v	               892635 file pages	
vmstat -v	                  0.0 compressed percentage	
vmstat -v	                    0 compressed pages	
vmstat -v	                 23.4 numclient percentage	
vmstat -v	                 90.0 maxclient percentage	
vmstat -v	               892635 client pages	
vmstat -v	                    0 remote pageouts scheduled	
vmstat -v	                  464 pending disk I/Os blocked with no pbuf	
vmstat -v	              1032267 paging space I/Os blocked with no psbuf	
vmstat -v	                 2484 filesystem I/Os blocked with no fsbuf	
vmstat -v	                 8944 client filesystem I/Os blocked with no fsbuf	
vmstat -v	                40125 external pager filesystem I/Os blocked with no fsbuf	
vmstat -s		
vmstat -s	          38982072456 total address trans. faults	


vmstat -s	           6100677571 page ins	
vmstat -s	           3108904883 page outs	
vmstat -s	              1528952 paging space page ins	
vmstat -s	             20919908 paging space page outs	
vmstat -s	                    0 total reclaims	
vmstat -s	          26582518377 zero filled pages faults	
vmstat -s	            109402572 executable filled pages faults	
vmstat -s	          14913211346 pages examined by clock	
vmstat -s	                21329 revolutions of the clock hand	
vmstat -s	           7596297938 pages freed by the clock	
vmstat -s	            422803868 backtracks	
vmstat -s	               165435 free frame waits	
vmstat -s	                    0 extend XPT waits	
vmstat -s	            171151807 pending I/O waits	
vmstat -s	           8362669434 start I/Os	

vmstat -s	            700404914 iodones	
vmstat -s	          80112710759 cpu context switches	
vmstat -s	           8015040200 device interrupts	
vmstat -s	           2288856611 software interrupts	
vmstat -s	          11017018086 decrementer interrupts	
vmstat -s	            181940861 mpc-sent interrupts	
vmstat -s	            170300017 mpc-receive interrupts	
vmstat -s	            697499545 phantom interrupts	


vmstat -s	                    0 traps	
vmstat -s	         311298592403 syscalls

OK, i have seen the output of two runs of "vmstat". What is it that you want to know, now?

"Tuning for performance" is a wide field and if your system is well tuned or not can't be answered from these data.

"Performance" is a term meaning "fitness for a specific purpose". As we don't know which purpose the system serves we can't tell if it is fit for this purpose or not.

If a vehicle is "fast" can only be answered once you specify the details of the movement involved: which streets (streets at all?), how much cargo to transport, distance involved, etc., etc.. The same goes for "performance": one would have to know, which applications the system runs, what it is expected to do and in which time and so on and so on.

And even if we would know which purpose the system serves and what else is running on it, there are still questions left: hardware resources (number of real and logical processors, disks, filesystems, I/O figures, OS version, network connections, .... the list could easily be continued.

Therefore: carefully rephrase your question, thinking over what exactly you want to know, what you already have in terms of data ("vmstat" was sure not the only command you tried, did you?) and what you want to achieve.

Then come back and ask again.

bakunin