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]>
