Sponsored Content
Operating Systems AIX Need to know %age disk busy on AIX Post 302887758 by bakunin on Monday 10th of February 2014 04:35:57 PM
Old 02-10-2014
Note, though, that "%tt_act" is NOT meaning the disk is taxed this amount of its bandwidth capacity. Especially "100%" does NOT MEAN it is at its limit.

It is like this: the disk (in fact its driver, but nevermind) maintains a queue where commands (like "fetch me some data", etc.) are stored until being executed. In regular intervals the OS queries the disk if this queue is empty or not. The "yes - empty"-answers and "no, not empty"-answers are computed to form a percentage and this percentage is "%tt_act".

While this value is indeed needed to assess the busyness of a disk it is meaningless if it is not combined with other data like averagy queue depth, size of the average read transaction and similar values.

Picture a movie theatres ticket counter: every 5 minutes you ask the clerk if there are people waiting in his queue or not. You do NOT ask if the queue is long or short, if the average customer buys one ticket or several, etc.. From the "yes" (queue bigger than 0) and "no" (queue is exactly 0) answers you compile the "busy" value, but it will not tell you how many people are watching the movie. For this you would need the other mentioned number too.

Back to the disk: if the disk is drowned in many very little requests it might be at 100% but the queue depth will always be very short and in fact a dramatic increase in requests will just make the average queue length a little bigger.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

Hard disk usage is 100 Percent Busy for any command

hi, AIX 5.3 For any command(say tar command) I am getting 100% busy for my hdisk. But my CPU and Memory is not busy and have more idle also. Please advice for any performance analysing. Thanks in Advance, (3 Replies)
Discussion started by: npcrao
3 Replies

2. Shell Programming and Scripting

Detailed disk usage versus age summary

Hi, I'm posting my question here as I fele that what I am about to try to do must have been done already, and I don't want to re-invent the wheel. I have recently become responsible for monitoring disk space usage for a large file system. I would like to geenrate reports that will summise... (8 Replies)
Discussion started by: littleIdiot
8 Replies

3. Shell Programming and Scripting

ksh - AIX: get epoch time/age for a file?

Hi, (AIX 5.1) Is there any way to find the epoch timestamp for a file without having to use fancy perl (or similar) scripts? If anyone knows of a way to do this using just ksh commands it would be appreciated. (It also appears I don't have the stat command available). Alternatively is... (3 Replies)
Discussion started by: b0bbins
3 Replies

4. AIX

all pseudo ttys busy, AIX 5.2

I have several users connecting via a Windows-based SSH\telnet client. The previous sysadmin used FacetTerm to allow certain users to switch between multiple "windows." I'm told there are AIX-native ways to do this but I work with what I inherited. Originally, many users were still connecting... (3 Replies)
Discussion started by: lacroix
3 Replies

5. UNIX for Advanced & Expert Users

Filesystem mystery: disks are not busy on one machine, very busy on a similar box

Hi, We have a filesystem mystery on our hands. Given: 2 machines, A and Aa. Machine Aa is the problem machine. Machine A is running Ubuntu, kernel 2.6.22.9 #1 SMP Wed Feb 20 08:46:16 CST 2008 x86_64 GNU/Linux. Machine Aa is running RHEL5.3, kernel 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38... (2 Replies)
Discussion started by: mschwage
2 Replies

6. Shell Programming and Scripting

Age of file in storage / disk

Hello all, Below is scripts to find the file following by: 30 days <- How many total file space within 30 days and not quantity 90 days 120 days 1 year From here also I can get data space to put on PIE Chart. Following this scripts can I do some enhance from this scripts like do... (1 Reply)
Discussion started by: sheikh76
1 Replies

7. Linux

How to Calculate Disk Queue length and Disk Busy Time

Hi, Am doing an enhancements related to monitoring a Linux disk I/O statistics. The /proc/diskstats file is used to get the each disk I/O statistics. But, It returns the raw value. How to calculate the Disk Queue Length and Disk Busy time from the raw values. Guide me. (1 Reply)
Discussion started by: maruthu
1 Replies

8. AIX

Clone or mirror your AIX OS larger disk to smaller disk ?

hello folks, I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies

9. AIX

Topas total Disk Busy %

Hi Everyone, anyone know how to derive the value for the total disk busy % (shown in topas ) ? Thanks. Best Regards, ckwan (1 Reply)
Discussion started by: ckwan
1 Replies

10. AIX

Command to check the busy % for a hard disk device like hdisk5

Please help with command to check the busy % for a hard disk device like hdisk5 Best regards, Vishal (7 Replies)
Discussion started by: Vishal_dba
7 Replies
RED(8)								       Linux								    RED(8)

NAME
red - Random Early Detection SYNOPSIS
tc qdisc ... red limit bytes min bytes max bytes avpkt bytes burst packets [ ecn ] [ bandwidth rate ] probability chance DESCRIPTION
Random Early Detection is a classless qdisc which manages its queue size smartly. Regular queues simply drop packets from the tail when they are full, which may not be the optimal behaviour. RED also performs tail drop, but does so in a more gradual way. Once the queue hits a certain average length, packets enqueued have a configurable chance of being marked (which may mean dropped). This chance increases linearly up to a point called the max average queue length, although the queue might get bigger. This has a host of benefits over simple taildrop, while not being processor intensive. It prevents synchronous retransmits after a burst in traffic, which cause further retransmits, etc. The goal is the have a small queue size, which is good for interactivity while not disturbing TCP/IP traffic with too many sudden drops after a burst of traffic. Depending on if ECN is configured, marking either means dropping or purely marking a packet as overlimit. ALGORITHM
The average queue size is used for determining the marking probability. This is calculated using an Exponential Weighted Moving Average, which can be more or less sensitive to bursts. When the average queue size is below min bytes, no packet will ever be marked. When it exceeds min, the probability of doing so climbs lin- early up to probability, until the average queue size hits max bytes. Because probability is normally not set to 100%, the queue size might conceivably rise above max bytes, so the limit parameter is provided to set a hard maximum for the size of the queue. PARAMETERS
min Average queue size at which marking becomes a possibility. max At this average queue size, the marking probability is maximal. Should be at least twice min to prevent synchronous retransmits, higher for low min. probability Maximum probability for marking, specified as a floating point number from 0.0 to 1.0. Suggested values are 0.01 or 0.02 (1 or 2%, respectively). limit Hard limit on the real (not average) queue size in bytes. Further packets are dropped. Should be set higher than max+burst. It is advised to set this a few times higher than max. burst Used for determining how fast the average queue size is influenced by the real queue size. Larger values make the calculation more sluggish, allowing longer bursts of traffic before marking starts. Real life experiments support the following guideline: (min+min+max)/(3*avpkt). avpkt Specified in bytes. Used with burst to determine the time constant for average queue size calculations. 1000 is a good value. bandwidth This rate is used for calculating the average queue size after some idle time. Should be set to the bandwidth of your interface. Does not mean that RED will shape for you! Optional. ecn As mentioned before, RED can either 'mark' or 'drop'. Explicit Congestion Notification allows RED to notify remote hosts that their rate exceeds the amount of bandwidth available. Non-ECN capable hosts can only be notified by dropping a packet. If this parameter is specified, packets which indicate that their hosts honor ECN will only be marked and not dropped, unless the queue size hits limit bytes. Needs a tc binary with RED support compiled in. Recommended. SEE ALSO
tc(8) SOURCES
o Floyd, S., and Jacobson, V., Random Early Detection gateways for Congestion Avoidance. http://www.aciri.org/floyd/papers/red/red.html o Some changes to the algorithm by Alexey N. Kuznetsov. AUTHORS
Alexey N. Kuznetsov, <kuznet@ms2.inr.ac.ru>, Alexey Makarenko <makar@phoenix.kharkov.ua>, J Hadi Salim <hadi@nortelnetworks.com>. This manpage maintained by bert hubert <ahu@ds9a.nl> iproute2 13 December 2001 RED(8)
All times are GMT -4. The time now is 01:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy