----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Ben,
>I had a question about optimizing the min and max process size
>directives in the jserv.properties file. One book suggested setting it
>to:
>-ms32m and -mx128m.
>
>Can these be tweaked any more? I thought I read that memory had
>something do with it. I have 256meg RAM in the server.
Play around with the settings and see what works best for your particular
setup. If you want to see what is happening with the garbage collection, add
to your jserv.properties file,
wrapper.bin.parameters=-Xms32m -Xmx128m
wrapper.bin.parameters=-verbosegc
JServ catches the gc machinations in the error.log. There is also a couple
of articles on the IBM site which explains some more about garbage
collection and how to use the gc to your advantage.
http://www-4.ibm.com/software/developer/library/tip-heap-size.html
http://www-4.ibm.com/software/developer/library/garbage-collection.html
The basic warning being that if you set the memory available to the JVM as
too high for your application it runs the risk of doing one big sweep as
opposed to many smaller ones. The one big sweep slowing or locking the JVM
until all the garbage is collected.
Hope that helps.
Cameron Riley
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
