|
Speaking only for myself, I will never turn off QPFRADJ. If you set appropriate limits it does its job well and there is no way manual tuning can keep abreast of your system as it changes throughout the day. The biggest problem I have noticed with QPFRADJ is that if you run an application in it's own storage pool you may have performance issues when the application starts and sufficient memory is not yet allocated to that pool. This can be easily solved by either manually moving the memory when you start the application or using WRKSHRPOOL to set a minimum size for that pool that is large enough for the app to start efficiently. We have the QINTER class set to a timeslice of 50. If you change your timeslice make sure that Eligible for purge is *YES and the system value QTSEPOOL is set to *BASE. Then you can watch jobs that exceed their timeslice move to the base pool in WRKACTJOB. Our batch timeslice remains at 5000. I also recommend moving all batch work into a separate shared pool. This includes things like HTTP servers, Domino and MQ Series. Instructions for this are here: http://www-912.ibm.com/s_dir/slkbase.nsf/3cdf5d853ca698198625680b00020369/56 28f38ef557e22f86256d6c00698fd9?OpenDocument&Highlight=2,separate,batch,base Every system is different, if your Wait->Inel and Active->Inel are both 0 and your faulting is relatively low you should be fine. My thoughts on pool activity levels (and I'm sure someone will correct me if I misspeak) are that if too high activity levels are causing problems you probably need more main storage. Regards, Scott Ingvaldson AS/400 System Administrator GuideOne Insurance Group -----Original Message----- date: Tue, 3 Feb 2004 05:44:08 -0800 from: "Graap, Ken" <keg@xxxxxxxxxxxxx> subject: RE: Auto Tuning So, what would you recommend as an appropriate timeslice setting for batch and interactive? Kenneth -----Original Message----- From: Clare Holtham [mailto:Clare.Holtham@xxxxxxxxxxxxxx] Sent: Monday, February 02, 2004 10:28 PM To: Midrange Systems Technical Discussion Subject: Re: Auto Tuning Ken, I think it's just one of those things like having the QINTER timeslice set to a value more appropriate for a B10, that IBM never gets round to fixing! And it's why you should, in my opinion, turn off automatic tuning and tune the system yourself. This is especially true if your applications use SQL! cheers, Clare This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.