× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. November 2013

Re: High Page Faulting in Base and Interactive Pools

No, it shouldn't _take_ memory from jobs that need it, but
it should _give_ memory to the jobs that need it, pulling it from *BASE. if you have diverse workloads (e.g. long running batch, short batch, java) all competing for memory in *BASE you may well have worse performance than you would have if you break out into pools...

Jim has a good lead to follow with Indexing, but I was able to help performance by breaking out my work into separate shared memory pools...


On 11/1/2013 2:37 PM, Joel Harvell wrote:
*Joel...
others will explain in better detail than me, but
you need to break out your subsystems from *BASE into *SHRPOOLs*...

I understand about moving SubSystems to other pools, but wouldn't that
actually take memory away from the jobs that need it. This system is very
sensitive to memory allocation. I want to be sure about the process and
the affects before I offer a pool configuration change.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.