I tested the jakarta-cache-tag when it was first released, but it was not working, well it displayed the cached-informations but it also ran the process behind the cached info, so it was of no real use.
I think it has been fixed, I might take a look at that. I dont know if OScache is JSP1.2 compliant, but it is compliant with Servlet 2.2 and JSP 1.1 standards according to the website http://www.opensymphony.com/oscache/features.html is tagpooling used if the tag-body contains other custom tags ? thanx -reynir > -----Original Message----- > From: peter lin [mailto:[EMAIL PROTECTED]] > Sent: 2. j�l� 2002 12:06 > To: Tomcat Users List > Subject: Re: Performance problems with tc4.0.4 and custom tags > > > > have you tried the jakarta cache tag? Perhaps try it with that first. > It could be the taglib is not compliant with JSP1.2. Also, I notice > OSCache tag examples use scriptlets. If I remember correctly from > discussion on tomcat-dev, tagpooling should be used only if > the tag body > doesn't contain scriplets. You should ask Remy or Kin-man to get the > authorative answer. > > peter > > > Reynir H�bner wrote: > > > > I have been playing a little bit around with jasper2 as > released with tc 4.1.6 and I am haveing problems. > > > > I am using the OSCache taglibrary, and for some reason this > does not work as it should. I cannot technically describe the > problem, as I have not dug into it, but the tags are > returning wrong values from cache. I think this has something > to do with the tagpooling feature as this was not a problem > in tc.4.1.3 version of jasper 2. > > > > just wanted to bounce that of to somewhere. hopefully > someone will pick this up, and check what's going wrong. > > > > [EMAIL PROTECTED] > > > > > -----Original Message----- > > > From: peter lin [mailto:[EMAIL PROTECTED]] > > > Sent: 2. j�l� 2002 11:19 > > > To: Tomcat Users List > > > Subject: Re: Performance problems with tc4.0.4 and custom tags > > > > > > > > > > > > I've been doing performance benchmarks and profiling of > jasper2 with > > > 4.0.3 and most indications tell me it's getting real close to > > > release. > > > Several tremendous improvements in jasper2 result in > better CPU and > > > memory utilization. GC is now under control and scales well to 64 > > > concurrent connections w/o any problems. On systems with more > > > memory and > > > multiple CPU's, the performance should be even better. > > > > > > The improvements I see in my profiling is speed and > > > consistency. when I > > > profiled jasper1 with tomcat 4.0.3, the cpu and memory utilization > > > fluctuated wildly, causing unusually high variance in > > > response time. GC > > > was horrible for pages with 100+ JSTL tags under 8+ concurrent > > > connections on a weak system. > > > > > > I'm not recommending anyone use it in production, but my personal > > > feeling is it is getting very close to release quality. > > > > > > peter > > > > > > > > > Timo Carl wrote: > > > > > > > > Hello, > > > > > > > > We try to upgrade our setup from tomcat3.2.1/jdk1.2 to > > > > tomcat4.0.4/jdk1.4. > > > > There were some major performance problems on our jsp > Pages that use > > > > 100+ custom tags. > > > > I've already read some other threads adressing this problem. > > > > > > > > But I wonder why tomcat3.2 with jasper1 does not have any > > > problems, but > > > > tomcat4. > > > > Any ideas? > > > > > > > > Has anyone experiences with using tomcat4.0.4/jasper2 in a > > > productive > > > > environment? > > > > Is it stable enough? > > > > > > > > Thanks in advance, > > > > Timo Carl > > > > > > > > -- > > > > Timo Carl > > > > Technik & Programmierung > > > > > > > > travelchannel GmbH > > > > Kehrwieder 8 > > > > D-20457 Hamburg > > > > Telefon +49/40/38617-275 > > > > Telefax +49/40/38617-330 > > > > > > > > http://www.travelchannel.de - das neue Reisen > > > > > > > > > > > > > > > > -- > > > > 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]> > > > > > > > > > > -- > > 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]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
