io utilization (average) on AIX


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting io utilization (average) on AIX
# 1  
Old 02-19-2008
io utilization (average) on AIX

Hi,
How can i find out the total average IO utilization over a period of time for a long-running process? on AIX

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

Need help on memory utilization.

I have run the utility nmon in aix 6.1, and found memory utilization is 99.9% in physical. and pressed h key and then t , in that it is not showing single process which is consuming memory resources. please help me how to find out actual memory utilization. wheather 99% is real memory... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

2. Red Hat

CPU Utilization and Memory Utilization of Services and Applications

Hi, i am new to linux/RHEL 6.0 and i have two questions. 1) How to get the CPU utilization and Memory Utilization of all Services running currently? 2) How to get the CPU utilization and Memory Utilization of all Applications running currently? Please help me to find the script. ... (2 Replies)
Discussion started by: nossam
2 Replies

3. AIX

What happened if CPU utilization is near to 100 % in AIX 6.1?

Hi all, We have a setup where our application is running on 2 AIX servers ( AIX 6.1 , 16 CPU, P5 570 boxes). These boxes works as disaster recovery server for each other i.e. in case of 1 box failure, whole load will run out of other box. Average CPU utilization on each box is between 30-40 %... (7 Replies)
Discussion started by: MKJ
7 Replies

4. Shell Programming and Scripting

Cpu utilization by a process has to be mailed if more than 5% on AIX

i am using the below command in order to find the cpu utilization by a user..now i want to mail if the cpu utilization goes beyond 5%....can someone please help me ? ps auxw | sort -r +2 | awk '{ print $3,$1 }' | head -6 | egrep "USER|#anonymous#" %CPU USER 2.0 anonymous Regards,... (6 Replies)
Discussion started by: arorap
6 Replies

5. AIX

Regarding AIX Memory Utilization usage calculation

Hello, Am working on small program that used to calculate the memory usage of AIX servers. Am using svmon -G command to get the memory usage. For example, consider the following output. $ svmon -G size inuse free pin virtual mmode memory ... (9 Replies)
Discussion started by: maruthu
9 Replies

6. AIX

How to calculate AIX CPU utilization using lparstat command

Could you please explain about calculate CPU utilization of aix server using lparstat command? Here below i have provided example output from aix test server. System configuration: type=Shared mode=Uncapped smt=On lcpu=4 mem=4096 psize=63 ent=0.50 %user %sys %wait %idle physc %entc ... (1 Reply)
Discussion started by: maruthu
1 Replies

7. Red Hat

FS Utilization Issue

Hi, I have inherited a server that is experiencing a FS utilization issue. The /home (below) is being utilized by the other mounted FS even though they belong to 2 different vg's. /dev/mapper/VolGroup00-home_vol 3.9G 3.7G 0 100% /home /dev/mapper/vg01-lvol0 394G 306G 68G 82%... (6 Replies)
Discussion started by: Duffs22
6 Replies

8. AIX

Find Memory Utilization in AIX Server

How to find the memory utilization of AIX server using svmon -G output. Sample output for svmon -G command from my AIX test server, size inuse free pin virtual memory 4014080 3995443 18637 575916 1876393 pg space 1179648 ... (3 Replies)
Discussion started by: maruthu
3 Replies

9. AIX

AIX 6.1 Power6 - Sys CPU utilization twice that of User

Hello, We just purchased two new 4-way (one active one failover) 5Ghz Power6 Servers (failover) with 64GB RAM (32GB per node) runing AIX 6.1 with two LPARs per node connected to our SAN with two 4GB HBAs. The PROD LPAR has 2 dedicated CPUs (4 virtual) and the TEST LPAR has 2 dedicated CPUs. ... (3 Replies)
Discussion started by: troym72
3 Replies

10. Solaris

Low average cpu utilization.

Hi to all, i have an app on solaris 5.8 writed in C++ (3.2.1) that use multi threading. Hardware has 8 cpu. When i run my app i note that the average of cpu go at least at 40%, and the performance are not so higher.. There is a cpu limitation on solaris, that dedicate only a part of cpu... (3 Replies)
Discussion started by: Moodie
3 Replies
Login or Register to Ask a Question
cpu_sup(3erl)						     Erlang Module Definition						     cpu_sup(3erl)

NAME
cpu_sup - A CPU Load and CPU Utilization Supervisor Process DESCRIPTION
cpu_sup is a process which supervises the CPU load and CPU utilization. It is part of the OS_Mon application, see os_mon(7) . Available for Unix, although CPU utilization values ( util/0,1 ) are only available for Solaris and Linux. The load values are proportional to how long time a runnable Unix process has to spend in the run queue before it is scheduled. Accord- ingly, higher values mean more system load. The returned value divided by 256 produces the figure displayed by rup and top . What is dis- played as 2.00 in rup , is displayed as load up to the second mark in xload . For example, rup displays a load of 128 as 0.50, and 512 as 2.00. If the user wants to view load values as percentage of machine capacity, then this way of measuring presents a problem, because the load values are not restricted to a fixed interval. In this case, the following simple mathematical transformation can produce the load value as a percentage: PercentLoad = 100 * (1 - D/(D + Load)) D determines which load value should be associated with which percentage. Choosing D = 50 means that 128 is 60% load, 256 is 80%, 512 is 90%, and so on. Another way of measuring system load is to divide the number of busy CPU cycles by the total number of CPU cycles. This produces values in the 0-100 range immediately. However, this method hides the fact that a machine can be more or less saturated. CPU utilization is therefore a better name than system load for this measure. A server which receives just enough requests to never become idle will score a CPU utilization of 100%. If the server receives 50% more requests, it will still scores 100%. When the system load is calculated with the percentage formula shown previously, the load will increase from 80% to 87%. The avg1/0 , avg5/0 , and avg15/0 functions can be used for retrieving system load values, and the util/0 and util/1 functions can be used for retrieving CPU utilization values. When run on Linux, cpu_sup assumes that the /proc file system is present and accessible by cpu_sup . If it is not, cpu_sup will terminate. EXPORTS
nprocs() -> UnixProcesses | {error, Reason} Types UnixProcesses = int() Reason = term() Returns the number of UNIX processes running on this machine. This is a crude way of measuring the system load, but it may be of interest in some cases. Returns 0 if cpu_sup is not available. avg1() -> SystemLoad | {error, Reason} Types SystemLoad = int() Reason = term() Returns the average system load in the last minute, as described above. 0 represents no load, 256 represents the load reported as 1.00 by rup . Returns 0 if cpu_sup is not available. avg5() -> SystemLoad | {error, Reason} Types SystemLoad = int() Reason = term() Returns the average system load in the last five minutes, as described above. 0 represents no load, 256 represents the load reported as 1.00 by rup . Returns 0 if cpu_sup is not available. avg15() -> SystemLoad | {error, Reason} Types SystemLoad = int() Reason = term() Returns the average system load in the last 15 minutes, as described above. 0 represents no load, 256 represents the load reported as 1.00 by rup . Returns 0 if cpu_sup is not available. util() -> CpuUtil | {error, Reason} Types CpuUtil = float() Reason = term() Returns CPU utilization since the last call to util/0 or util/1 by the calling process. Note: The returned value of the first call to util/0 or util/1 by a process will on most systems be the CPU utilization since system boot, but this is not guaranteed and the value should therefore be regarded as garbage. This also applies to the first call after a restart of cpu_sup . The CPU utilization is defined as the sum of the percentage shares of the CPU cycles spent in all busy processor states (see util/1 below) in average on all CPUs. Returns 0 if cpu_sup is not available. util(Opts) -> UtilSpec | {error, Reason} Types Opts = [detailed | per_cpu] UtilSpec = UtilDesc | [UtilDesc] UtilDesc = {Cpus, Busy, NonBusy, Misc} Cpus = all | int() | [int()]() Busy = NonBusy = {State, Share} | Share State = user | nice_user | kernel | wait | idle | atom() Share = float() Misc = [] Reason = term() Returns CPU utilization since the last call to util/0 or util/1 by the calling process, in more detail than util/0 . Note: The returned value of the first call to util/0 or util/1 by a process will on most systems be the CPU utilization since system boot, but this is not guaranteed and the value should therefore be regarded as garbage. This also applies to the first call after a restart of cpu_sup . Currently recognized options: detailed : The returned UtilDesc (s) will be even more detailed. per_cpu : Each CPU will be specified separately (assuming this information can be retrieved from the operating system), that is, a list with one UtilDesc per CPU will be returned. Description of UtilDesc = {Cpus, Busy, NonBusy, Misc} : Cpus : If the detailed and/or per_cpu option is given, this is the CPU number, or a list of the CPU numbers. If not, this is the atom all which implies that the UtilDesc contains information about all CPUs. Busy : If the detailed option is given, this is a list of {State, Share} tuples, where each tuple contains information about a processor state that has been identified as a busy processor state (see below). The atom State is the name of the state, and the float Share represents the percentage share of the CPU cycles spent in this state since the last call to util/0 or util/1 . If not, this is the sum of the percentage shares of the CPU cycles spent in all states identified as busy. If the per_cpu is not given, the value(s) presented are the average of all CPUs. NonBusy : Similar to Busy , but for processor states that have been identified as non-busy (see below). Misc : Currently unused; reserved for future use. Currently these processor states are identified as busy: user : Executing code in user mode. nice_user : Executing code in low priority (nice) user mode. This state is currently only identified on Linux. kernel : Executing code in kernel mode. Currently these processor states are identified as non-busy: wait : Waiting. This state is currently only identified on Solaris. idle : Idle. Note: Identified processor states may be different on different operating systems and may change between different versions of cpu_sup on the same operating system. The sum of the percentage shares of the CPU cycles spent in all busy and all non-busy processor states will always add up to 100%, though. Returns {all,0,0,[]} if cpu_sup is not available. SEE ALSO
os_mon(3erl) Ericsson AB os_mon 2.2.5 cpu_sup(3erl)