We have been doing some performance measurements over the last week. We saw significant improvement by increasing our pool sizes so that the objects were not being recreated over and over.
Ralph -----Original Message----- From: Ugo Cei [mailto:[EMAIL PROTECTED] Sent: Friday, April 30, 2004 5:07 AM To: [EMAIL PROTECTED] Subject: Re: XMLSerializer poolable? Alexandre Victoor wrote: > Moreover, looking at the code, I wonder if it really useful for this > component to be poolable. It does not look like expensive in term of > memory/cpu to create an instance of XMLSerializer. Articles as > http://www-106.ibm.com/developerworks/library/j-jtp01274.html claims > that recycling object is not always a good thing. > > It is also something more to take in account when tuning cocoon. If it were for me, I'd drop the Poolable and Recyclable interfaces *NOW*, but things aren't that easy. See http://marc.theaimsgroup.com/?t=107640906000001&r=1&w=2 for an interesting thread on the subject. Ugo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
