Costin Manolache <[EMAIL PROTECTED]> wrote:
On the other hand, I've seen pages where JSP tag pooling was worse.
That's why I think per page customization, and supporting per-thread pooling
are very important. This is a "fine-tune" operation for pages that are
frequently accessed, not a "one siz
ormance improvement
> under load.
>
> Marc
>
>> -Original Message-
>> From: Glenn Nielsen [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, July 08, 2003 9:25 AM
>> To: Tomcat Developers List
>> Subject: Object pooling performance
>>
&
Glenn Nielsen wrote:
> Remy Maucherat wrote:
>> Bill Barker wrote:
>>
>>> Now, if we could only convince the Jasper developers of this ... ;-).
>>
>>
>> Tag pooling is definitely not the same situation and use case as session
>> pooling. Tag pooling *is* useful in many cases.
>>
>
> There are
[EMAIL PROTECTED]
> Sent: Tuesday, July 08, 2003 3:18 PM
> To: Tomcat Developers List
> Subject: Re: Object pooling performance
>
> Marc Saegesser wrote:
> > Another thing to consider when evaluating object pooling is the expected
> > lifetime of the objects. On mo
Peter Lin wrote:
I second remy's summary. from first hand experience with JSP with 200 tags,
tag pooling provide significant performance improvement. From what I saw in
OptimizeIt, with jasper1 and 200+ tags per page, garbage collection was happening
frequently and full GC was occuring way too ofte
Marc Saegesser wrote:
Another thing to consider when evaluating object pooling is the expected
lifetime of the objects. On modern JVMs with generational memory stores,
objects with a short lifespan (say the duration of a single HTTP request)
will probably never leave the nursery. Pooling these ki
Glenn Nielsen wrote:
Remy Maucherat wrote:
There are a number of things to consider when evaluating the performance of
object pooling.
The performance hit of obtaining/recycling an object can be greater than
instantiating a new object, it depends on the JVM.
But you also have to consider the impact
I second remy's summary. from first hand experience with JSP with 200 tags, tag
pooling provide significant performance improvement. From what I saw in OptimizeIt,
with jasper1 and 200+ tags per page, garbage collection was happening frequently and
full GC was occuring way too often.
with ta
2003 9:25 AM
To: Tomcat Developers List
Subject: Object pooling performance
Remy Maucherat wrote:
Bill Barker wrote:
Now, if we could only convince the Jasper developers of this ... ;-).
Tag pooling is definitely not the same situation and use case as session
pooling. Tag pooling *is* useful in ma
CTED]
> Sent: Tuesday, July 08, 2003 9:25 AM
> To: Tomcat Developers List
> Subject: Object pooling performance
>
> Remy Maucherat wrote:
> > Bill Barker wrote:
> >
> >> Now, if we could only convince the Jasper developers of this ... ;-).
> >
> >
> &g
Remy Maucherat wrote:
Bill Barker wrote:
Now, if we could only convince the Jasper developers of this ... ;-).
Tag pooling is definitely not the same situation and use case as session
pooling. Tag pooling *is* useful in many cases.
There are a number of things to consider when evaluating the p
11 matches
Mail list logo
