Re: How much memory is currently paged?

[DrFranken <midrange@xxxxxxxxxxxx>]

Depends on the system (CPUs, total memory) the faulting numbers here 
could be acceptable but they are significant. Pool 2 (*BASE) is showing 
more than one in four pages as a fault that's not a great ratio. Pool 5 
is very poor with about 80% of pages faulting. Need more meory there 
almost certainly. Pool 4 is very good with 0.03% of pages faulting and 
that's with a LOT of paging!  The machine pool ration is poor also with 
almost seven of eight pages faulting but the numbers are pretty low 
overall there so not a huge problem.

If it was me, I would be investigating more memory for this system or 
potentially fewer jobs running in pool 2 and 5.

Of course additional performance work with the iDoctor tools or MPG's 
tools will help get more refined answers.

I don't believe QTEMP is in there, that space is tracked differently as 
I recall.

    - Larry "DrFranken" Bolhuis

On 8/14/2012 9:26 AM, rob@xxxxxxxxx wrote:
> So on this system:
> Current unprotect used . :   118375 M
> Maximum unprotect  . . . :   123112 M
> Sys      Pool   Reserved    Max  ----DB-----  --Non-DB---  Act-   Wait-
> Act-
> Pool    Size M   Size M     Act  Fault Pages  Fault Pages  Wait   Inel
> Inel
>    1    5119.48   1304.85  +++++     .0    .0   66.7  82.7  106.7     .0
> .0
>    2   24095.87    184.31   1880     .0    .0  280.2 834.5  57437     .0
> .0
>    3     683.43       .49     28     .0    .0     .0    .0   1174     .0
> .0
>    4   14697.73      1.15   1547   17.7 58241   14.2  16.9   3042     .0
> .0
>    5   16266.90       .09    157     .0    .0  169.9 202.8     .0     .0
> .0
>    6    7480.57      4.57    800     .0    .0     .0    .0  19217     .0
> .0
> The "overall" is good.  Wait-Inel and Act-Inel are zero.  So far so good.
> And with 1.2TB disk free and 52 disk arms disk isn't being affected by
> paging.  Highest %busy is 11.  Now it's just determining "if faulting is
> acceptable".
>
> But on this system
> System ASP . . . . . . :    352.8 G
> % system ASP used  . . :    81.3364
> Total  . . . . . . . . :    352.8 G
> Current unprotect used :    14839 M
> Maximum unprotect  . . :    18332 M
> System    Pool
>   Pool   Size (M)
>     1      619.92
>     2    10371.64
>     3      111.17
>     4       15.25
> Even though faulting/paging are nil at this time, (WAS startup was last
> night) it would be a concern.  But, the ratio of current unprotect used to
> actual memory is actually better than on the larger system.  This smaller
> system only has 6 disk arms but they are only peaking at 1% busy.
>
> Not just paging goes into "current unprotect" right?  Isn't QTEMP and all
> that rot in there?  The bigger system would have a lot more of that genre.
>   The smaller system is reserved for WAS and Domino only.  No ERP or
> "traditional applications".
>
>
>
> Rob Berendt