Howdy,
On the 5.0.16 profile just 2 requests to the webapp made the heap
profile
have a scale of 100-200MB being used. Now on 5.0.18 it is 10-30MB.
This is a very good change, to use far less memory. I'm wondering what
your pages do that two requests need that much memory, but that's
besides
with 5.0.16 vs 5.0.18 Strange behaviour
Howdy,
On the 5.0.16 profile just 2 requests to the webapp made the heap
profile
have a scale of 100-200MB being used. Now on 5.0.18 it is 10-30MB.
This is a very good change, to use far less memory. I'm wondering what
your pages do that two requests need
Allistair Crossley wrote:
I read about the leak and some other posts but it seemed that Remy
did not consider it to be anything many people would run into or even
a big leak.
The leak can be significant in some cases. But it's easy to avoid on
5.0.16 (increase maxSpareThreads), and you'll need a
]
Sent: 21 January 2004 17:21
To: Tomcat Users List
Subject: Re: JProfiler with 5.0.16 vs 5.0.18 Strange behaviour
Allistair Crossley wrote:
I read about the leak and some other posts but it seemed that Remy
did not consider it to be anything many people would run into or even
a big leak
Allistair Crossley wrote:
Hey,
How would you explain what I have posted about JProfiler for 5.0.16
and 5.0.18? That was just 2 people traffic on a development box!!
5.0.16 was consuming over 100MB and now it does not go above 30MB.
The memory used by this release should be equivalent.
Your
