What 'good reasons' did you have in mind?
Serge posted an article today that discusses this issue in some detail. See "Explicit Nulling" in http://www-106.ibm.com/developerworks/java/library/j-jtp01274.html.
Java performance has few absolutes. For example, the author of that article is not a fan of user-level object pooling. Neither, for that matter, is the J2SE tech lead. However, when we added object pooling of certain objects in James, we found that performance improved significantly under load.
The section on object pooling was refuting the pervasive notion that object pool used to avoid object creation/collection will improve performance.
It does in no way suggest pooling in general is bad, in fact, "When the object creation cost is high, such as with database connections or threads, or the pooled object represents a limited and costly resource, such as with database connections, this makes sense."
-- Serge Knystautas President 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]
