Re: High Page Faulting in Base and Interactive Pools

simply, as it was explained to me..
pick a subsystem, or in some cases (I haven't gone this far...) jobs (should I split out my QZDASOINIT DB jobs out to its own pool???)


step one... measure how it performs now (WRKSYSSTS)
Step two... follow the work management guide to put your subsystem into a shared pool.
step three... measure again.

I started with my QHTTPSVR subsystem, then moved on to QSYSWRK and QUSRWRK...

Gerald


On 11/1/2013 3:29 PM, Mitchell, Dana wrote:

Given the more modern hardware and the abundance of memory now days, how important is it to break memory into several pools? Wouldn't the OS be better at moving memory between jobs that humans could be?

Given that, if this system needs a 'major overhaul', how exactly does one determine size and assignments of the pools?

Dana


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Friday, November 01, 2013 3:12 PM
To: Midrange Systems Technical Discussion
Subject: 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.

--

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.



Attention: This electronic document and associated attachments (if any) may contain confidential information of the sender (SHAZAM Network) and is intended solely for use by the addressee(s). Review by unintended individuals is prohibited. If you are not the intended recipient: (i) do not read, transmit, copy, disclose, store, or utilize this communication in any manner; (ii) please reply to the sender immediately, state that you received it in error and permanently delete this message and any attachment(s) from your computer and destroy the material in its entirety if in hard copy format. If you are the intended recipient, please use discretion in any email reply to ensure that you do not send confidential information as we cannot secure it through this medium. By responding to us through internet e-mail, you agree to hold SHAZAM, Inc. and all affiliated companies harmless for any unintentional dissemination of information contained in your message. Thank you. (2)