ADSM-L

Re: Memory Tuning For AIX

2002-01-02 14:49:50
Subject: Re: Memory Tuning For AIX
From: "Richard L. Rhodes" <rhodesr AT FIRSTENERGYCORP DOT COM>
Date: Wed, 2 Jan 2002 14:46:28 -5
I'd trust more experienced help, but here
are my thoughts . . .

pi + po indicate you are constantly paging.  This probably
means you need more memory, but could be caused by aggressive
aix filesystem caching.  If so, vmtune can help limit
filesystem caching.

Your cpu is hardly being hit.  us + sy is only
around 25%. The majority of your cpu time
is wa - waiting for I/O - processes blocked on
disk I/O.

My suggestion is more disks for more disk i/o bandwidth and
more memory.  An iostat will tell you which disks/filesystems
need to be spread across more disk drives.

Rick

On 2 Jan 2002 at 13:33, Denis L'Huillier wrote:
> Hello-
> I am having a memory problem.
> I am runnning AIX 4.3.2 on a H50.  TSM is the only application
> running on the server.  When I run vmstat I get the following...
>
> kthr     memory             page              faults        cpu
> ----- ----------- ------------------------ ------------ -----------
>  r  b   avm   fre  re  pi  po  fr   sr  cy  in   sy  cs us sy id wa
>  0  0 136233   202   0   3   2  99  210   0  52  240  66 17 30 16 37
>  1  3 136234   342   0  38  11 3727 4204   0 1322 6136 4665 12 11  3 74
>  2  3 136236   160   0  44  12 3728 5326   0 1324 5844 4644 10 11  2 76
>  1  3 136237   295   0  17  19 4113 5725   0 1305 7174 5091 13 10  3 74
>  0  3 136237   629   0  19   9 4240 7442   0 1316 7200 5082 14 13  5 68
>
> Does this look normal to anyone?  From my limited understanding of vmstat
> it looks like:
> CPU utilization is maxed out
> I have blocked processes (the b column)
> The scan rate (sr) column is very high.
> The server has 1Gig of memory.  I'm really not sure how to tell how much is
> allocated to
> the OS and how much is allocated to TSM.  Does anyone have any ideas or
> pointers is
> tuning memory for AIX?  Do I need a memory upgrade?
> I started checking this because my server response is horrible.
> Thanks.
> Denis
>
<Prev in Thread] Current Thread [Next in Thread>