Remy Maucherat wrote:
>
> > Since include directive is like C include. I originally though include
> > directive would always perform better than action include. For one
> > thread, include directive does perform better, but 2 threads action
> > include is twice as fast. One interesting observation with coyote
> > include directive for 1 thread is 95% of the responses were 30ms, but
> > the standard deviation or variance is almost 3x the mean. Other noteable
> > observations for 1 thread is include directive see dramatic fluctuations
> > in cpu and memory usage. This suggests JSP tags create and destroy lots
> > of objects associated with parsing and processing.
>
> The 1 thread test could be really unpredictable (if GC happens, it will just
> stop all requests during that time, which will greatly increase the
> average). That's the only explnation I can think of.
>
I downloaded an eval of JProbe just now, so hopefully next week I can
get you more data on what's happening. If indeed the load performance is
a result of over active GC and excessive object instantiation, tuning
the java parameters in conjunction with pooling tag classes should
dramatically improve the performance.
Right now if my jsp files use 50 when tags, it creates a new instance of
WhenTag 50 times. Along with that, each tag that uses test to evaluate
an expression also creates an instance of an expression parser. In the
current JSTL expression language support classes, it doesn't create a
pool of expression parsers. If I have time, I will write an expression
manager that creates a pool of parsers and recycles them.
I have some extreme performance requirements, so efficiency under high
load is a must :)
peter lin
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
