--- Bill Barker <[EMAIL PROTECTED]> wrote: > From what I've seen, for small number of requests > like this, the overhead of > managing the tagpool swamps what it saves in GC. > You might want to try > disabling tag-pooling (and clear the work dir), and > re-run the test on 4.1.
Object pooling is just bad design and it should be removed from the spec. We don't pool StringBuffers or HashSets or whatever because that results in crappy performance. Object pooling used to be a good idea way back in the Java 1.1 days but now, with the exception of very expensive objects like database connections, object pooling makes performance worse. The GC is very very effecient and it does a better job than an object pool can do. Also, pooling Tag objects can result in various kinds of bugs that are essentially memory management type of bugs. One of the main reasons we are using Java instead of C++ is _because_ of the GC. We should use it, not fight it. I hope that Tag pooling is removed entirely from the spec soon. __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
