If you restart the web server (and mid-tier) without first clearing the cache, the mid-tier reads in the exiting persistent pre-fetch cache file (takes about 1 minute on our servers). Only if you flush the cache in the mid-tier configuration tool and then restart the mid-tier will the complete pre-fetch run (takes 24 minutes on our servers). The persistent pre-fetch only works properly on 7.1.00.002 and later; earlier releases did not re-read the existing pre-fetched cache properly after a restart, especially after a tomcat crash and restart.
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Sreenivas, Aravind Sent: Thursday, November 20, 2008 6:03 AM To: [email protected] Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat ** We recently observed that when we restart our app/web server (Tomcat/Apache), majority of the files in the cache directory (*.data and *.index) are updated (<tomcat>/webapps/ars/cache). We have enabled persistent cache option and have a few of the biggest forms in pre-fetch. 1. For forms mentioned in the prefetch xml, am I correct in assuming that : a. these are fetched when I start/restart the app/web server AND the other forms (i.e. those not mentioned in the prefetch xml) are not fetched? b. The forms not mentioned in the prefetch are fetched only when a user tries to access the forms and its out-of-date (assuming Enable check is switched on)? 2. Is there any way in which we can tell the app/web server not to fetch forms (either mentioned in prefetch or not) when we restart the app/web server? We would like it to use what data it already has in the cache directory before it was restarted, rather than it fetching the forms from the server again after its restarted. 3. What is the purpose of the USERNAME in the prefetch xml? Should only an admin username be defined here or will any ID do? I skimmed through the documentation available, but was unable to get clarity on the above. ARS 7.1 patch 003 on solaris MT 7.1 patch 005 on apache 2_2/tomcat 5-5.5.25 Thanks Aravind ________________________________ From: "Easter, David" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> To: [email protected]<mailto:[email protected]> Sent: Wednesday, November 19, 2008 6:50:50 PM Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat ** The use of persistent cache is so that you don't have to go fetch again after the Mid-Tier is restarted. BMC Remedy Mid Tier performance (persistent cache) In AR System 7.1, forms currently cached in memory can now be serialized to a file, which enables these forms to be read back into memory when the application server hosting the mid tier application is restarted (after a normal shutdown). Pre-fetch is for when the forms haven't yet been fetched. It ensures that the fetching occurs prior to the first request for the form. That way, users don't have to wait for the Mid-Tier to fetch the form - it's already there and cached for them. -David J. Easter Sr. Product Manager, Solution Strategy and Development BMC Software, Inc. The opinions, statements, and/or suggested courses of action expressed in this E-mail do not necessarily reflect those of BMC Software, Inc. My voluntary participation in this forum is not intended to convey a role as a spokesperson, liaison or public relations representative for BMC Software, Inc. __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
