Here are some thoughts
Shawn Bayern wrote:
>
> On Fri, 22 Mar 2002, peter lin wrote:
>
>
> Interesting thought, Peter.
>
> Given that instantiating an Evaluator object involves no specific logic on
> construction, the only cost of not having a pool is that of object
> creation itself, wh
On Fri, 22 Mar 2002, Shawn Bayern wrote:
> The evaluator keeps a static cache of values, so literally the only
> benefit of pooling our interpreter instances would be to save the
> instantiation itself, which should take about ten low-level instructions
> on a modern JIT. (That is, the evaluator
On Fri, 22 Mar 2002, peter lin wrote:
> I've been doing benchmarks with JSTL on some dynamic pages and noticed
> under medium & heavy load 4-64 concurrent connections, the performance
> degrades rapidly. I looked at ExpressionEvaluatorManager and it looks
> like it doesn't create a pool of parse
