All, You will have a seen a handful of changes over the last few days related to performance and garbage generation. I wanted to provide a little background.
As part of testing the new Resources implementation I have been running the follow ab test: ab -c 4 -k -n 1000000 http://localhost:8080/test-1k.txt where test1k-txt is a 1024 byte text file. I have then been observing Tomcat with YourKit to determine where the bottlenecks are and also comparing it to trunk. I have been using both CPU and object allocation profiling. When looking at the results for trunk there have been a number of obvious hot spots, particularly in object allocation. These have generally been caused by objects being created per request. Where there has been a simple way to reduce this, I have done so. There are a few more places to review. I have tried to keep the fixes simple - there are some hot spots that could be addressed but I have not done so as they require more invasive changes. I may revisit these as the more I fix other issues, the greater impact these issues have. The nature of the testing so far means that there are bound to be many code paths that I have missed. However, as I expand the performance testing for the new Resources implementation I hope to expand the coverage of the profiling as well. In terms of back-porting to 7.0.x, I have not reached a conclusion on whether to back-port or not. Thoughts? Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
