At 02:19 PM 4/17/00, Michael Anderson wrote:
>Here's some data I received from GLANCE <Memory Detail
>screen>. How bout those clock-cycles? and are these the
>same clock-cycles that  you are referring too?
>
>------------------------------------------------------------------------------
>Page Overlay Candidate Rate    31.8/sec
>System Library Page Faults      0.0/sec
>Memory Mgr Clock Cycle Rate         144
>Physical Memory Size             256 mb
>--------------------------------------------------------------------------------
>Afew minutes later, the clock-cycle was at 760
>--------------------------------------------------------------------------------
>Page Overlay Candidate Rate    41.4/sec
>System Library Page Faults      0.6/sec
>Memory Mgr Clock Cycle Rate         760
>Physical Memory Size             256 mb
>--------------------------------------------------------------------------------

Yes, these are the same clock cycles I was referring to last week.  It's
very clear from these numbers that you are seriously short of main
memory.  As a reminder, if the clock cycle rate of the memory manager
exceeds 25 per hour you have memory pressure.  When you have memory
pressure, memory-resident pages are swapped out more rapidly than is
healthy for good throughput.  Swapping out data pages is bad enough.  Your
memory problem is forcing the memory manager to actually swap out library
(XL's and SL's, primarily) pages.  This is *really* bad!  This shifts the
memory pressure out of simply affecting I/O performance and into affecting
program execution performance.

How much memory should you have on this system???  It depends.  (I had to
work it in somewhere!) :-)

Seriously, I would consider a gigabyte, or more, of memory.  If you have
having this bad of memory pressure at 256 megabytes, you are in a fairly
desperate situation.

HTH,

Bill