> -----Original Message----- > From: Costin Manolache [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 5:49 PM > To: [EMAIL PROTECTED] > Subject: Re: DO NOT REPLY [Bug 16001] - Tag.release() not invoked > > > Hans Bergsten wrote: > > > evaluation all in one place. To make things even easier, these tag > > handlers can _not_ be reused at all. Benchmarks with modern > JVMs show > > that the gain from reuse is not worth all the trouble. So, for new > > tags we recommend using the SimpleTag API which takes care of the > > problem by forbidding reuse. > > Wow. I would be _very_ curious to see those benchmarks and > the "modern" JVM that was used. > > All my tests ( including JDK1.4, IBM vms, GCJ ) show that > reusing is well worth the trouble - at least if you have 100s > of requests per second ( it is not worht the trouble for very > low loads ). But I'm happy to hear that I'm wrong. > > Costin
I thought the benefit of Tag.release and pooling was that I could create a tag that does something expensive at init time (acquire a DB connection, read a file, whatever) and reuse those resources until released. Maybe that's a bad practice? But then what's the advantage of having release called only once before GC? -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
