× 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.






Just a few thoughts:

- subsystems and pools are designed to isolate workloads and provide for
separate control over each individual workload type.
If you think that your workload cannot be subdivided into distinct types
and/or you do not want to isolate these workloads, then you can live with
just two pools - *MACHINE pool for system purposes and *BASE for the rest.

- basic cycle for QPFRADJ is 20 seconds. It needs at least a couple of
cycles to see the pattern of use and take an action.
I do not think that QPFRADJ can take any action in "very few seconds".

- storage for the pool is allocated when the first subsystem which uses the
pool, starts.
If *SHRPOOL1 had significant storage size configured for it, and then you
started a subsystem in *SHRPOOL1, the pool will have storage allocated to
it all at once. This indeed can happen very quickly.

- QPFRADJ treatment of different pools is determined by pool tuning
attributes (basically second page in WRKSHRPOOL).
The further pool is from its target, the more aggressive QPFRADJ will be.


    Alexei
always speaking for myself



                                                                                
                                 
                      rob@dekko.com                                             
                                 
                      Sent by:                    To:       Midrange Systems 
Technical Discussion                
                      midrange-l-bounces@m         <midrange-l@midrange.com>    
                                 
                      idrange.com                 cc:                           
                                 
                                                  Subject:  Why not *SHRPOOL1?  
                                 
                                                                                
                                 
                      01/27/2003 08:10 AM                                       
                                 
                      Please respond to                                         
                                 
                      Midrange Systems                                          
                                 
                      Technical Discussion                                      
                                 
                                                                                
                                 
                                                                                
                                 




On our 840 12-way we have system value QPFRADJ set to "2=Adjustment at IPL
and automatic adjustment".  And we have the following pools:
System    Pool    Reserved    Max
 Pool   Size (M)  Size (M)  Active  Pool
   1     2618.98    655.60   +++++  *MACHINE
   2     6307.05     55.12     530  *BASE
   3     3935.35      <.01      80  *SHRPOOL1
   4      303.44       .00      20  *SPOOL
   5     1835.15       .20     227  *INTERACT

Actually, this does a pretty good job.  However, if you start this big
whopping job in one subsystem, or the other, then it takes awhile until
QPFRADJ switches memory over.  In the Rochester lab (just last week) we
had a Query take 3 minutes until we switched QINTER to run in *SHRPOOL1.
They were still scratching their heads to figure out how often QPFRADJ
adjusts.  After the switch it took only a very few seconds.

So now my boss asked me a good question.  Why don't we just use two pools:
 *MACHINE and *SHRPOOL1?  And avoid that time lag of QPFRADJ.

Questions and comments appreciated.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.