From: Nicholas S. <ni...@sa...> - 2002-07-07 18:33:30
|
Nick You're probably completely correct. The performance gain probably comes from creating far fewer objects and not having to configure each new object, as the overhead of maintaining the pool means that for smaller numbers of invocations non pooled is faster. I created a simple servlet and used both pooled and non pooled implementations. As the load increases the pooled implementation shows fewer non available errors and probably takes up less memory. I haven't really had time to run exhaustive trials. I've implemented the pool so that it is basically an add on rather than intrinsic to FormProc. The underlying implementation is the jakarta-commons pool -so if it's fundamentally sound the credit is all theirs. Think of it not as redesigning the bow but as being an extra arrow in your quiver ;-) As Anthony said, it's not really core FormProc stuff but at least if anyone asks if you've considered pooling there's an example of how it could be done ( or of the folly of trying :-) ) Regards Nick |