04-22-2009
how to identified this iostat value
Hi All AIX expert
i'm using AIX 5.2
When i execute this command which is :
----------------------------------------------------------------------
>> iostat -a
System configuration: lcpu=4 disk=30
tty: tin tout avg-cpu: % user % sys % idle % iowait
0.1 7.9 80.6 2.0 17.1 0.4
" Disk history since boot not available. "
----------------------------------------------------------------------
In linux, if the % idle is below 20%, then the explanation is "If '%idle' goes below 20%, the system maybe queuing up disk I/Os and response time suffers."
But i'm not sure with AIX, what does that % idle represent and the rest such as % user and % iowait....
When i have above read, does that mean my disk I/O in a danger situation??
8 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
All,
I am attempting to help tune a Sun for better performance (mainly for SAS 9.1), and have found indicators pointing to poor I/O utilization. I have run iostat -cx, and found one device in particular where the %w is in the 90's during processing. I have a feeling that this is where the SAS... (3 Replies)
Discussion started by: dj_is
3 Replies
2. Solaris
Sorry for asking basics. What exactly is the situation if device ID is same in iostat -Eni. What we must do then? Is there any relation b/w iostat and cfgadm? (3 Replies)
Discussion started by: mayahari
3 Replies
3. Shell Programming and Scripting
Friends.
I have to compare iostat -x output with a tool on solaris. Now there is column called wait in the output field which is showing zero. Now, in order to create some load on my system this is what i am doing
I am creating a file using dd command , the size of which is... (5 Replies)
Discussion started by: achak01
5 Replies
4. Red Hat
A find for the "iostat" command on a redhat 5 update 4 comes back with no results.
Any separate rpm needs to be installed to get the binary for this ?
Thanks in advance. (1 Reply)
Discussion started by: uxadmin007
1 Replies
5. Solaris
I all,
I would like to know what are the causes of :
-soft error
-harderror
-transport error
and how to avoid and repare them.
I got the iostat out put below:
atng-mm01% iostat -En | grep -i hard
c0t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
c0t0d1 ... (3 Replies)
Discussion started by: zaza
3 Replies
6. Solaris
Hello everyone,
Can you please explain me what kind of information do IOSTAT show ?
iostat -xnz 3 show me those informations:
The I/O of the c0t0d0 disk is normal ?
extended device statistics
r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device
0.0 ... (3 Replies)
Discussion started by: adilyos
3 Replies
7. AIX
Hello, I support Oracle 11g on AIX 7.1.
Using the command
$iostat -D hdisk2 hdisk4 hdisk5 5
I get the following output:
hdisk5 xfer: %tm_act bps tps bread bwrtn
44.0 1.4M 178.2 1.4M 14.7K
read: ... (3 Replies)
Discussion started by: oracledba1024
3 Replies
8. Shell Programming and Scripting
In the perl one-liner below I am identifying the runs of 6a or 6A in each line starting with >. The code seems close but it prints each > line no matter if it has 6a or 6A in it. Only the line with the 6a or 6A needs to be printed.
So using the input file, only the >hg19_refGene_NM_001918_3... (10 Replies)
Discussion started by: cmccabe
10 Replies
LEARN ABOUT SUSE
glutidlefunc
glutIdleFunc(3GLUT) GLUT glutIdleFunc(3GLUT)
NAME
glutIdleFunc - sets the global idle callback.
SYNTAX
void glutIdleFunc(void (*func)(void));
ARGUMENTS
func The new idle callback function.
DESCRIPTION
glutIdleFunc sets the global idle callback to be func so a GLUT program can perform background processing tasks or continuous animation
when window system events are not being received. If enabled, the idle callback is continuously called when events are not being received.
The callback routine has no parameters. The current window and current menu will not be changed before the idle callback. Programs with
multiple windows and/or menus should explicitly set the current window and/or current menu and not rely on its current setting.
The amount of computation and rendering done in an idle callback should be minimized to avoid affecting the program's interactive response.
In general, not more than a single frame of rendering should be done in an idle callback.
Passing NULL to glutIdleFunc disables the generation of the idle callback.
EXAMPLE
A typical idle callback to animate a window might look like:
void
idle(void)
{
time += 0.05;
glutSetWindow(window);
glutPostRedisplay();
}
Notice how the idle callback does not do any actual drawing; it only advances the time scene state global variable. That is left to the
window's display callback which will be triggered by the call to glutPostRedisplay.
If you use the idle callback for animation, you should be sure to stop rendering when the window is not visible. This is easy to set up
with a visibility callback. For example:
void
visible(int vis)
{
if (vis == GLUT_VISIBLE)
glutIdleFunc(idle);
else
glutIdleFunc(NULL);
}
If you do use the idle callback for animation, one thing you should not do is setup the idle callback before calling glutMainLoop. It is
much better to use the visibility callback to install idle callback when the window first becomes visible on the screen.
SEE ALSO
glutTimerFunc, glutVisibilityFunc
AUTHOR
Mark J. Kilgard (mjk@nvidia.com)
GLUT
3.7 glutIdleFunc(3GLUT)