I removed pretty much everything I could from server.xml.
Removing JMX listeners improved the initial startup time but Tomcat still uses significant more memory and memory usage grows faster when performing similar tests comparing to Jetty (to a certain point after each it is no growing so this is not a memory leak)


I modified minProcessors to 1 and MaxProcesors to 2. not sure what it is and how it is being used.
Here is an O[Reilly "Demystifying Tomcat 4's server.xml File" article, not much help for me.
http://www.onjava.com/lpt/a/1618
Is minSpareThreads some server.xml properties?


Thanks for help Kris.

Shapira, Yoav wrote:

Howdy,
You want to take out everything you don't need from server.xml.  That
includes Connectors, Loggers, Realms, Valves, JNDI entries, etc.  Do you
expect to use the Manager webapp?  If not, you can remove it as well as
it's not required for tomcat to work properly.

For your (hopefully just one) remaining connector, reduce the number of
spare threads (set minSpareThreads=maxSpareThreads=1) as well as the
acceptCount.

If you need less (or more) than 64MB of RAM, specify what you need via
the JAVA_OPTS variable in the startup scripts.

Yoav Shapira
Millennium ChemInformatics




-----Original Message-----
From: Kris Gemborys [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 03, 2003 1:13 PM
To: Tomcat Users List
Subject: Tunning up Tomcat to run web application on desktops in the


single


user environment with limitted resources

First I want to apologize for another of these mails "what is better
jetty vs tomcat' but most of the available resources compare both
containers in the environment where they are serving multiple


concurrent


requests. What I am interested is the container that utilizes as little
resources as possible and is the most responsive while running on
Pentium III or low-end Pentium 4 laptop with small amount of RAM


serving


single user. My limited knowledge about both products does not allow me
to perform any type of container configuration beyond of lowering
maximum number of threads for jetty.

Here is what I have done so far and my results:
Windows XP Professional/Pentium 4 M - 2 Ghz/Tomcat 4.1.24/Jetty
4.2.15/JDK 1.4.1
Prototype application uses XSLT/XML/Cloudscape with no connection


pooling


I removed all preinstalled Tomcat web applications except Manager.
I also removed bunch of other files from Jetty, Tomcat and SUN's JDK
packages which helped me to create two distributable 20 MB zips for


both


JDK/Tomcat and JDK/ Jetty.
I deployed a prototype application to both Jetty and Tomcat.
I precompiled all jsp for both Jetty and Tomcat - fortunately they both
are using jasper :-)
I have observed that Jetty starts and loads application at least twice
faster and uses 25% less memory. The pages were rendered within 1 sec.
I am not using <load-on-startup>. to conserve RAM.

Does anybody have comments on this topic?
Are there any Tomcat specific hints to improve its performance and
reduce amount of utilized resources assuming that it is being used by a
single user?

Thanks for help, Kris.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to