Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4477144D.5050107@tngtech.com>
Date: Fri, 26 May 2006 16:44:29 +0200
From: Michael Echerer <mech@tngtech.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: problem in GC tuning
References: <013f01c322b2$97f4c5f0$9009a8c0@prashant>
In-Reply-To: <013f01c322b2$97f4c5f0$9009a8c0@prashant>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Prashant kumar wrote:
> Hi All,

>  
>  1)  Is there any means  by which GC takes less CPU,  I mean that it
> can take longer time to complete  its one cycle (as memory is not a
> constraint) ? 

You've set quite a lot of heap 3400m. Do you really need that much
memory? The more you set, the more the GC needs to scan. If it's unused
however, try reducing Xmx and Xms to values that are sufficient for your
app.
Then try to size the generations to get smaller chunks to be scanned and
check the survivor ratios.

Give the incremental GC a try. Might get worse, but probably it works.

http://java.sun.com/docs/hotspot/gc1.4.2
>  
> 2)  Do writing of logs at higher loads have some impact on the
> performance?
>  
You should definitely disable GC logging in production, if you don't
need it for diagnosis anylonger.

Cheers,
Michael


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org