Hi,
In TomCat's source code, I notice it recycles objects (e.g. RequestBase,
StandardSession). But in Sun's documentation, with HotSpot Virtual machine,
pooling objects will hinder performance (see below). Could someone please
tell me are there advantages of using object pooling in TomCat?
On Wed, 14 Nov 2001, Samuel Cheung wrote:
Hi,
In TomCat's source code, I notice it recycles objects (e.g. RequestBase,
StandardSession). But in Sun's documentation, with HotSpot Virtual machine,
pooling objects will hinder performance (see below). Could someone please
tell me are there
There are several reasons to use pooling, including (but not limited
to):
-Eliminating object creation time
-Managing expensive resources (really same as first)
-Keeping memory usage constant (popular in embedded environments)
-Reducing garbage collection
Only the last one is addressed by the
[EMAIL PROTECTED] wrote:
Turning off recycling is quite easy ( just few lines to comment
to prevent reseting the objects and reusing it ).
The performance didn't go up - but down, about 30% ( under
reasonable load ).
The probable reason being that memery management isn't the only factor
