Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Solaris Performance Monitoring

Solaris Performance Monitoring

Ratings: (0)|Views: 8 |Likes:
Published by Biswajit Das

More info:

Published by: Biswajit Das on Jul 31, 2013
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Solaris Performance Monitoring &Tuning - iostat , vmstat & netstat
Introduction to iostat , vmstat and netstat
This document is primarily written with reference to solaris performance monitoring andtuning but these tools are available in other unix variants also with slight syntaxdifference. 
, vmstat and netstat are three most commonly used tools for performancemonitoring . These comes built in with the operating system and are easy to use .iostatstands for input output statistics and reports statistics for i/o devices such as disk drives .vmstat gives the statistics for virtual Memory and netstat gives the network statstics .Following paragraphs describes these tools and their usage for performance monitoringand if you need more information there are some very good solaris performancemonitoring books available at
Table of content :
Input Output statistics ( iostat )
iostat reports terminal and disk I/O activity and CPU utilization. The first line of output is for the time period since boot & each subsequent line is for the prior interval . Kernel maintains a number of counters to keep track of the values.iostat's activity class options default to tdc (terminal, disk, and CPU). If any other option/s are specified, this default is completely overridden i.e. iostat -d will reportonly statistics about the disks. 
Basic synctax is i
ostat <options> interval count 
$ iostat -xtc 5 2extended diskstatistics tty cpudisk r/s w/s Kr/s Kw/s wait actv svc_t %w%b tin tout us sy wt idsd0 2.6 3.0 20.7 22.7 0.1 0.2 59.2 619 0 84 3 85 11 0sd1 4.2 1.0 33.5 8.0 0.0 0.2 47.2 223sd2 0.0 0.0 0.0 0.0 0.0 0.0 0.0 00sd3 10.2 1.6 51.4 12.8 0.1 0.3 31.2 331 The fields have the following meanings:disk name of the diskr/s reads per secondw/s writes per secondKr/s kilobytes read per second
Kw/s kilobytes written per secondwait average number of transactionswaiting for service (Q length)actv average number of transactionsactivelybeing serviced (removed from thequeue but not yetcompleted)%w percent of time there aretransactions waitingfor service (queue non-empty)%b percent of time the disk is busy(transactionsin progress)
Results and Solutions:
The values to look from the iostat output are:
Reads/writes per second (r/s , w/s)
Percentage busy (
Service time (
)If a disk shows consistently high reads/writes along with , the percentage busy (
) of thedisks is greater than 5 percent, and the average service time (
) is greater than 30milliseconds, then one of the following action needs to be taken
Tune the application to use disk i/o more efficiently by modifying the disk queriesand using available cache facilities of application servers .
Spread the file system of the disk on to two or more disk using disk striping featureof volume manager /disksuite etc.
Increase the system parameter values for inode cache , ufs_ninode , which is Number of inodes to be held in memory. Inodes are cached globally (for UFS), not on a per-file system basis
Move the file system to another faster disk /controller or replace existingdisk/controller to a faster one.
Virtual Memory Statistics ( vmstat )

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->