Re: High Page Faulting in Base and Interactive Pools

I would most certainly agree that the memory allocation on this system needs a major overhaul, not a minor one, major. The current configuration is the source of the sensitivity to memory changes, not the reason for it. That said, something that recently happened to upset a system needs to be dealt with first, then come back and set up the work management the way this system needs it.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 11/1/2013 3:00 PM, Gqcy wrote:

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.

--