I just ran some benchmarks with 4.1.6 and noticed a couple of things.
1. 4.1.6 is showing less of an impact once the connector reaches the max processors. With 4.0.3, I was able to trigger a out of memory error by letting JMeter continue for a couple minutes after tomcat reaches the max processors and is denying connections. I discovered this by accident when I was running benchmarks with 120 con current connection hitting pages with lots of JSTL tags. the max processor was set to 75. 2. performance appears to be more consistent memory and cpu wise. Under moderate and heavy load, the cpu usage varies more with 4.0.3 and it takes longer for 4.0.3 to return to normal memory usage. This was done with just task monitor and not optimizeIt or JProbe since I can't get JProbe to work correctly with jasper2. 3. tag pooling does show 5-10% improvement over jasper2 w/o tag pooling. Once I figure out how to get JProbe to work with jasper2, i will run more tests. peter --- Remy Maucherat <[EMAIL PROTECTED]> wrote: > Hightlights in this test release include: > - fix for a memory leak in the request dispatcher > - many fixes and refactorings in Jasper 2 > - admin webapp improvements > - other misc fixes > > See the release notes for the list of changes. > > Downloads: > http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.6/ > > Remy > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
