absolutely. I think for most cases the current implementation is sufficient, but for your high-rate of create/destroy of runtime instances I can see why this might be a problem.
WILL On 3/1/06, Serge Knystautas <[EMAIL PROTECTED]> wrote: > > I did some memory profiling, and for each runtime instance, by default > it creates 20 parsers. According to yourkit, each parser uses just > over 100kb heap space, so each runtime instance is costing me 2mb heap > space. > > I can simply reduce the # of parsers, but the problem is that simple > pool is a very, very primitive pool implementation... it holds a > constant number parsers and if you exceed, it simply creates and > disposes a parser (ballpark of 1ms per parser instantiation in my > benchmarks). > > I'd like to convert simplepool to an interface and then make the > current behavior an impl so that you could swap in something like > commons pool. Is there interest in such a patch? > > -- > Serge Knystautas > Lokitech >> software . strategy . design >> http://www.lokitech.com > p. 301.656.5501 > e. [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- _______________________________________ Forio Business Simulations Will Glass-Husain phone (415) 440-7500 x89 mobile (415) 235-4293 [EMAIL PROTECTED] www.forio.com
