Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Sreenivas, Aravind]

Thank you, all, for your responses.

 

Aravind

 

 

 

On Thu, Nov 20, 2008 at 9:57 PM, strauss <[EMAIL PROTECTED]> wrote:

** 

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/

 

 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[strauss]

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: arslist@ARSLIST.ORG
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 
(/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: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
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"

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[SPrasad]

Hi Aravind,

In the prefetchconfig.xml we only define Demo and appadmin user accounts.
Using Demo or appadmin users for prefetchig would be enough to have a
configuration usefull for most of your users.

Thanks
SPrasad


Sreenivas, Aravind wrote:
> 
>  
> 
> 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 (/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]>
> To: arslist@ARSLIST.ORG
> 
> 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.
> 
>  
> 
>  
> 
> 
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Mid-Tier-7.1.0-Performance-IssueTomcat-tp20587205p20604874.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Joe DeSouza]

Aravind,

It uses the persistent cache by default after a restart of the web server 
unless the stop of the web server had been caused by a crash - that is my 
understanding of persistent cache.

I believe the reason it doesn't use the persistent cache if the web server 
crashes is that the crash may have been caused by a corruption in the cache, so 
it flushes and rebuilds the cache..

Joe





From: "Sreenivas, Aravind" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Thursday, November 20, 2008 7:02:51 AM
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 
(/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]>
To: arslist@ARSLIST.ORG
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.




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Sreenivas, Aravind]

 

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 (/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]>
To: arslist@ARSLIST.ORG

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.

 

 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Joe DeSouza]

Cool, for some reason I was under the impression that persistent cache was 
designed to do away with pre-fetching altogether. From your explanation and 
extract from documentation it appears like it is designed to collaborate with 
pre-fetch to further improve the overall performance..

Thanks for the correction.

Cheers

Joe





From: "Easter, David" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
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 
applicationserver 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.




From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Wednesday, November 19, 2008 3:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

** 
What is the use of persistent cache then? I thought that was introduced to do 
away with that initial hit of choking up the server during a startup where it 
takes forever to build its cache.

I did notice that the prefetch xml file was still available but hadn't really 
bothered configuring it as persistent cache kept our cache intact on disk 
during any web server restarts..

Joe





From: "Easter, David" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, November 19, 2008 5:31:52 PM
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

** 
> 7.1 doesn't use pre-fetch to the best of my knowledge.. 
 
AR System 7.1.00 definitely provides an ability to do pre-fetch.  In fact, 
7.1.00 is the first release where it was formally supported.  Here's a 
cut/paste from the "What's New in AR System 7.1.00" document:
 
Prefetching specified forms
Administrators can select forms to be preloaded into the system’s 
memory(prefetched) so that forms can be loaded faster when they are opened in a 
browser.This capability is especially useful for larger forms that otherwise 
might takeseveral seconds to load.  Forms can be selected for prefetching 
eitherby editing the prefetchConfig.xml file, available in the 
web-inf/classesdirectory.from the BMC Remedy Configuration Tool, or
 
The What's New document can be found here:
 
06-Aug-2007 What’s New: BMC Remedy Action Request System 7.1.00 PDF
 
 
-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.



From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Wednesday, November 19, 2008 12:12 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

** 
Change the Resource Check Interval to greater than that - make it about 604800 
that equate to 7 days rather than a day that you have there..

7.1 doesn't use pre-fetch to the best of my knowledge.. That was good until 
7.0. Check the Persistent Cache option instead on 7.1 which basically stores 
all your server cache on disk so if the web server is shut down gracefully, it 
uses the same cache that is on disk the next time it is brought up.

It blows the cache away from the disk only in case of a web server crash..

Adjust the java initial and maximum heap size (-Xms & -Xmx). The recommended 
maximum heap size should be no greater than 65 to 70% of the 'total available 
free memory' before Tomcat is started. Its good to have about 30 to 35% 
headroom or you would crash your tomcat server even while starting it or it 
might crash when and if you want to stop it. Your initial size should be at 
least 

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Easter, David]

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.
 
 


From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Wednesday, November 19, 2008 3:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat


** 
What is the use of persistent cache then? I thought that was introduced to do 
away with that initial hit of choking up the server during a startup where it 
takes forever to build its cache.
 
I did notice that the prefetch xml file was still available but hadn't really 
bothered configuring it as persistent cache kept our cache intact on disk 
during any web server restarts..
 
Joe




From: "Easter, David" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, November 19, 2008 5:31:52 PM
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

** 
> 7.1 doesn't use pre-fetch to the best of my knowledge.. 
 
AR System 7.1.00 definitely provides an ability to do pre-fetch.  In fact, 
7.1.00 is the first release where it was formally supported.  Here's a 
cut/paste from the "What's New in AR System 7.1.00" document:
 
Prefetching specified forms

Administrators can select forms to be preloaded into the system’s memory 
(prefetched) so that forms can be loaded faster when they are opened in a 
browser. This capability is especially useful for larger forms that otherwise 
might take several seconds to load.  Forms can be selected for prefetching 
either

from the BMC Remedy Configuration Tool, or

by editing the prefetchConfig.xml file, available in the web-inf/classes 
directory.

 
The What's New document can be found here:
 
06-Aug-2007 What’s New: BMC Remedy Action Request System 7.1.00 PDF 
<http://www.bmc.com/supportu/documents/17/53/71753/71753.pdf>  
 
 
-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.
 


From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Wednesday, November 19, 2008 12:12 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat


** 
Change the Resource Check Interval to greater than that - make it about 604800 
that equate to 7 days rather than a day that you have there..
 
7.1 doesn't use pre-fetch to the best of my knowledge.. That was good until 
7.0. Check the Persistent Cache option instead on 7.1 which basically stores 
all your server cache on disk so if the web server is shut down gracefully, it 
uses the same cache that is on disk the next time it is brought up.
 
It blows the cache away from the disk only in case of a web server crash..
 
Adjust the java initial and maximum heap size (-Xms & -Xmx). The recommended 
maximum heap size should be no greater than 65 to 70% of the 'total available 
free memory' before Tomcat is started. Its good to have about 30 to 35% 
headroom or you would crash your tomcat server even while starting it or it 
might crash when and if you want to stop it. Your initial size should be at 
least about 1024 M. If that is over the 65 to 70% headroom that you need, then 
your server resources aren't enough - consider up sizing your server..
 
If you still see out of memory errors on the catalina.out file that causes your 
tomcat application server to crash, implement the 'incremental garbage 
collection' (-Xincgc). This helps your tomcat server to free up memory by 
clearing unused portions of its memory (least used portions).
 
Let

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Joe DeSouza]

What is the use of persistent cache then? I thought that was introduced to do 
away with that initial hit of choking up the server during a startup where it 
takes forever to build its cache.

I did notice that the prefetch xml file was still available but hadn't really 
bothered configuring it as persistent cache kept our cache intact on disk 
during any web server restarts..

Joe





From: "Easter, David" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, November 19, 2008 5:31:52 PM
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

** 
> 7.1 doesn't use pre-fetch to the best of my knowledge.. 
 
AR System 7.1.00 definitely provides an ability to do pre-fetch.  In fact, 
7.1.00 is the first release where it was formally supported.  Here's a 
cut/paste from the "What's New in AR System 7.1.00" document:
 
Prefetching specified forms
Administrators can select forms to be preloaded into the system’s 
memory(prefetched) so that forms can be loaded faster when they are opened in a 
browser.This capability is especially useful for larger forms that otherwise 
might takeseveral seconds to load.  Forms can be selected for prefetching 
eitherby editing the prefetchConfig.xml file, available in the 
web-inf/classesdirectory.from the BMC Remedy Configuration Tool, or
 
The What's New document can be found here:
 
06-Aug-2007 What’s New: BMC Remedy Action Request System 7.1.00 PDF
 
 
-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.



From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Wednesday, November 19, 2008 12:12 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

** 
Change the Resource Check Interval to greater than that - make it about 604800 
that equate to 7 days rather than a day that you have there..

7.1 doesn't use pre-fetch to the best of my knowledge.. That was good until 
7.0. Check the Persistent Cache option instead on 7.1 which basically stores 
all your server cache on disk so if the web server is shut down gracefully, it 
uses the same cache that is on disk the next time it is brought up.

It blows the cache away from the disk only in case of a web server crash..

Adjust the java initial and maximum heap size (-Xms & -Xmx). The recommended 
maximum heap size should be no greater than 65 to 70% of the 'total available 
free memory' before Tomcat is started. Its good to have about 30 to 35% 
headroom or you would crash your tomcat server even while starting it or it 
might crash when and if you want to stop it. Your initial size should be at 
least about 1024 M. If that is over the 65 to 70% headroom that you need, then 
your server resources aren't enough - consider up sizing your server..

If you still see out of memory errors on the catalina.out file that causes your 
tomcat application server to crash, implement the 'incremental garbage 
collection' (-Xincgc). This helps your tomcat server to free up memory by 
clearing unused portions of its memory (least used portions).

Let me know if any of these help..

Cheers

Joe





From: SPrasad <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, November 19, 2008 2:20:50 PM
Subject: Mid-Tier 7.1.0 Performance Issue -- Tomcat

Hi All,

We are getting slow response from Server and we are looking for ways to improve 
our server performance.

I have made the following changes in the Mid-Tier configuration tool.

Cache Settings:

1) Uncheck the perform check box
2) Change the Resource Check Interval from the default of 300 seconds to 86400 
seconds 

Reporting:

1) Log Level: For best performance, this value should be set to SEVERE. 
2) We are logging only Reporting.

There are few more recommedations I saw in the documentation and those are 

1) arsystem.pooling_max_connections_per_server: Default is 80. Change to 1000 
2) arsystem.pooling_max_total_connections: Change to 2000.

And also, I have updated the prefetchconfig.xml file with all the forms that we 
use regularly.

Below is our Environment Info:

AR Server Ver:7.1.0 Patch002
Mid-Tier: 7.1.0 Patch002
Web Server Information: Apache Tomcat/5.5.26
Java Version: 1.5.0_13
O/S: Linux
Database:Oracle 10.2.0.4

Does anyone have some type of documentation or tips or recommendations for 
enhancing the performance of Mid-Tier version 7.1.0 Patch002?

Any help is really appreciated.

Thanks
SPrasad


 

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Easter, David]

> 7.1 doesn't use pre-fetch to the best of my knowledge.. 
 
AR System 7.1.00 definitely provides an ability to do pre-fetch.  In
fact, 7.1.00 is the first release where it was formally supported.
Here's a cut/paste from the "What's New in AR System 7.1.00" document:
 
Prefetching specified forms

Administrators can select forms to be preloaded into the system's memory
(prefetched) so that forms can be loaded faster when they are opened in
a browser. This capability is especially useful for larger forms that
otherwise might take several seconds to load.  Forms can be selected for
prefetching either


 from the BMC Remedy Configuration Tool, or


 by editing the prefetchConfig.xml file, available in the
web-inf/classes directory.

 
The What's New document can be found here:
 
06-Aug-2007 What's New: BMC Remedy Action Request System 7.1.00
PDF <http://www.bmc.com/supportu/documents/17/53/71753/71753.pdf>  
 
 
-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.
 


From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
Sent: Wednesday, November 19, 2008 12:12 PM
To: arslist@ARSLIST.ORG
Subject: Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat


** 
Change the Resource Check Interval to greater than that - make it about
604800 that equate to 7 days rather than a day that you have there..
 
7.1 doesn't use pre-fetch to the best of my knowledge.. That was good
until 7.0. Check the Persistent Cache option instead on 7.1 which
basically stores all your server cache on disk so if the web server is
shut down gracefully, it uses the same cache that is on disk the next
time it is brought up.
 
It blows the cache away from the disk only in case of a web server
crash..
 
Adjust the java initial and maximum heap size (-Xms & -Xmx). The
recommended maximum heap size should be no greater than 65 to 70% of the
'total available free memory' before Tomcat is started. Its good to have
about 30 to 35% headroom or you would crash your tomcat server even
while starting it or it might crash when and if you want to stop it.
Your initial size should be at least about 1024 M. If that is over the
65 to 70% headroom that you need, then your server resources aren't
enough - consider up sizing your server..
 
If you still see out of memory errors on the catalina.out file that
causes your tomcat application server to crash, implement the
'incremental garbage collection' (-Xincgc). This helps your tomcat
server to free up memory by clearing unused portions of its memory
(least used portions).
 
Let me know if any of these help..
 
Cheers
 
Joe




From: SPrasad <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, November 19, 2008 2:20:50 PM
Subject: Mid-Tier 7.1.0 Performance Issue -- Tomcat

Hi All,

We are getting slow response from Server and we are looking for ways to
improve our server performance.

I have made the following changes in the Mid-Tier configuration tool.

Cache Settings:

1) Uncheck the perform check box
2) Change the Resource Check Interval from the default of 300 seconds to
86400 seconds 

Reporting:

1) Log Level: For best performance, this value should be set to SEVERE. 
2) We are logging only Reporting.

There are few more recommedations I saw in the documentation and those
are 

1) arsystem.pooling_max_connections_per_server: Default is 80. Change to
1000 
2) arsystem.pooling_max_total_connections: Change to 2000.

And also, I have updated the prefetchconfig.xml file with all the forms
that we use regularly.

Below is our Environment Info:

AR Server Ver:7.1.0 Patch002
Mid-Tier: 7.1.0 Patch002
Web Server Information: Apache Tomcat/5.5.26
Java Version: 1.5.0_13
O/S: Linux
Database:Oracle 10.2.0.4

Does anyone have some type of documentation or tips or recommendations
for enhancing the performance of Mid-Tier version 7.1.0 Patch002?

Any help is really appreciated.

Thanks
SPrasad

__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"

Re: Mid-Tier 7.1.0 Performance Issue -- Tomcat

[Joe DeSouza]

Change the Resource Check Interval to greater than that - make it about 604800 
that equate to 7 days rather than a day that you have there..

7.1 doesn't use pre-fetch to the best of my knowledge.. That was good until 
7.0. Check the Persistent Cache option instead on 7.1 which basically stores 
all your server cache on disk so if the web server is shut down gracefully, it 
uses the same cache that is on disk the next time it is brought up.

It blows the cache away from the disk only in case of a web server crash..

Adjust the java initial and maximum heap size (-Xms & -Xmx). The recommended 
maximum heap size should be no greater than 65 to 70% of the 'total available 
free memory' before Tomcat is started. Its good to have about 30 to 35% 
headroom or you would crash your tomcat server even while starting it or it 
might crash when and if you want to stop it. Your initial size should be at 
least about 1024 M. If that is over the 65 to 70% headroom that you need, then 
your server resources aren't enough - consider up sizing your server..

If you still see out of memory errors on the catalina.out file that causes your 
tomcat application server to crash, implement the 'incremental garbage 
collection' (-Xincgc). This helps your tomcat server to free up memory by 
clearing unused portions of its memory (least used portions).

Let me know if any of these help..

Cheers

Joe





From: SPrasad <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, November 19, 2008 2:20:50 PM
Subject: Mid-Tier 7.1.0 Performance Issue -- Tomcat

Hi All,

We are getting slow response from Server and we are looking for ways to improve 
our server performance.

I have made the following changes in the Mid-Tier configuration tool.

Cache Settings:

1) Uncheck the perform check box
2) Change the Resource Check Interval from the default of 300 seconds to 86400 
seconds 

Reporting:

1) Log Level: For best performance, this value should be set to SEVERE. 
2) We are logging only Reporting.

There are few more recommedations I saw in the documentation and those are 

1) arsystem.pooling_max_connections_per_server: Default is 80. Change to 1000 
2) arsystem.pooling_max_total_connections: Change to 2000.

And also, I have updated the prefetchconfig.xml file with all the forms that we 
use regularly.

Below is our Environment Info:

AR Server Ver:7.1.0 Patch002
Mid-Tier: 7.1.0 Patch002
Web Server Information: Apache Tomcat/5.5.26
Java Version: 1.5.0_13
O/S: Linux
Database:Oracle 10.2.0.4

Does anyone have some type of documentation or tips or recommendations for 
enhancing the performance of Mid-Tier version 7.1.0 Patch002?

Any help is really appreciated.

Thanks
SPrasad




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"