----------------------------------------------------------------
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!!!
----------------------------------------------------------------
At 9:20 AM -0700 8/2/00, Don Pierce wrote:
>I have an additional 50 meg of memory so I bumped the memory
>to ms48 mx72 from ms32 mx64 and I am getting far less GCverbose
> cleanings - so far.
I have to say that we are seeing some of the same behavior, although
I haven't turned on verbose GC logging yet.
Even bumping up the memory partition enormously (the machine has 1GB)
just defers the problem. And then you are gc'ing a very large heap.
We are looking at ways to reduce memory usage in our main servlet,
but the concurrency issue is killing us during peak traffic times. I
also observe that the JVM timeout seems to be independent of the
setting in the jserv.properties. Haven't had a chance to look into
it.
I suspect the solution will be basic good profiling and fixing of
memory hogging code, to reduce the load on the gc thread.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
