----- Original Message ----- From: "Remy Maucherat" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Saturday, January 18, 2003 12:36 AM Subject: Re: DO NOT REPLY [Bug 16001] - Tag.release() not invoked
> Bill Barker wrote: > > I saw just the opposite. Jasper2 with tag-pooling was a real dog (the time > > spent in synchronized methods to maintain the pool completely swamped any > > benefit from GC). After patching my copy to make don't-tag-pool the default > > (since there isn't any way to do this in the config :( ), then Tomcat > > 4.1/Jasper2 was about 60% faster that Tomcat 3.3/Jasper1 when I 'ab' > > benchmarked it against one of my more complex pages. > > There's a switch in the conifguration to enable/disable tag pooling, > actually. I'm quite sure it works fine. > http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html > > Personally, some quick test I had done showed tag pooling to be fatster > on my configuration. > Yeah, well, almost all of my JSP pages are defined by: <servlet> <servlet-name>somename</servlet-name> <jsp-page>/somepath/somepage.jsp</jsp-page> </servlet> And I can assure you that the params for JspServlet don't work at all (unless I take the totally brain-dead path of including the Jasper params in my own servlets). If tag-pooling works for you, I'm happy for you. The current implementation doesn't work for me big time. However, I'm very interested in Costin's claim that it can be done thread-local. > Remy > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
