Re: Expert Cache

<snip>
OTOH, expert cache maintains a sliding window for determining its 
settings - 4 minutes, I think. DB sends the info anyway, I think, so 
there is not a complete savings in CPU cycles by turning off expert 
cache. I might be inclined to turn it on, so that it can optimize 
things when it can.
</snip>

Since so much I/O generally goes through *BASE due to the lack of tuning 
on the ODBC and JDBC jobs, I would turn on the expert cache and leave it 
on.  The only time I have found expert cache to be detrimental is if the 
CPU is truly bound, and then I did not want to spend the cycles (small as 
they are) to compute the page sizes etc.   I usually leave the dynamic 
priority scheduler and adjustment  turned on as well as performance adjust 
at value "3", performance adjust (no IPL information ).  This has proven 
to be the best overall strategy for most machines.

The only down side to performance adjust, is it tends to get overzealous 
taking memory away from *MACHINE and *BASE in favor of interactive.  For 
those machines I tweak the pool tuning values to even things out a bit. 

Jim