Thanks for the tips Jon.
I am going to start working on suggestions 1), 2), 4), 5) right away. The point on 3)
looks interesting - hopefully I'll have time profile GC. 6) is out of my hands. I have
already tried 7). I am not sure about 8) - what are the listeners you are referring to
? I My application doesn't make use of servlet listeners.
Thanks for the tips - much appreciated!
Tarun
-----Original Message-----
From: Jon Barnett [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 30, 2003 7:14 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] JBoss Performance Tuning Tips - a bit of an
emergency
Have you tried the following?
1) Build an optimized version of JBoss.
2) Used different JVMs - IBM SDK best on Linux. YMMV.
3) Check GC with -verbose:gc and tune accordingly - there has been one
report that a Sun JVM distributed GC performed full GC with RMI operations
on every collection cycle, slowed
by -Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 (I think he ended up applying
this -Dsun.rmi.dgc.server.gcInterval=0x7FFFFFFFFFFFFFFE
-Dsun.rmi.dgc.client.gcInterval=0x7FFFFFFFFFFFFFFE
-XX:+DisableExplicitGC). You can also avoid the by removing the JRMP
Invoker if you are not using it.
4) Modify the hsqldb-ds.xml to use the in-process or in-memory operation
(comments in the file), or remove it entirely if you are using your own
DB.
5) Remove sub-systems you do not use - such as the http-invoker, the
scheduler and so on.
6) Try with different versions of the JDBC driver or get a third-party
driver (performance can vary)
7) Tune the EJB pool sizes - either globally in standardjboss.xml or in
the local jboss.xml (maximumSize definition and
<strictMaximumSize>true</strictMaximumSize>)
8) Remove listeners you do not use in the servlet container
I guess that is a start.
Regards,
JonB.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Elankath,
> Tarun (Cognizant)
> Sent: Friday, 29 August 2003 11:01 PM
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] JBoss Performance Tuning Tips - a bit of an
> emergency
>
>
> Hi all,
>
> We have a small web + ejb application for a POC (Proof of
> Concept) that is competing against a corresponding .NET
> application. We are using Struts, 1 Stateful Session Bean, 1
> Stateless Session Bean and only 10 JSP pages. The application
> connects to a separate MS-SQL database server.
>
> This application is being deployed in WebSphere, JBoss across
> Windows and Linux as the target servers.
>
> So far, JBoss is giving the worst results on a 1000 user stress
> test, which I am certain is ENTIRELY due to my inexperience with
> this application server, and nothing whatsover to do with jboss.
>
> All performance tips on tuning jboss config parameters will be
> much appreciated. I have done the following:
> -increased ms and mx heap size
> -increased connection pool size
> -increase maxProcessor,minProcessor setting (for Tomcat)
> -decreased session timeouts.
> -made log level to ERROR in log4.xml
>
> I am still now sure on how to disable class reloading totally.
>
>
> All tips/suggestions will be deeply appreciated. If JBoss
> performs good, then our client would definitely prefer .Net to
> Java, just for the cost factor.
>
> Regards,
> Tarun
>
>
>
This e-mail and any files transmitted with it are for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message.
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or
copying of this email or any action taken in reliance on this e-mail is strictly
prohibited and may be unlawful.
Visit us at http://www.cognizant.com
