On 18/02/2016 22:57, Ty wrote: > I've re-run my tests using 8.0.x trunk (8.0.33-dev) using the same > procedure from the first message of this thread, and summarized the results > below. Heap usage is vastly improved both with and without JAR scanning. > Heap size and startup time are both reasonable and it's now feasible to > re-visit our upgrade plan, so we will be putting 8.0.33 into our next cycle > (once it's officially released). > > Thanks again for looking into this, and wow, addressing it so quickly.
Great. That is good news. I'm not finished with this. There were a number of things in the heap dump that looked to be worthy of further consideration. I hope to get to them in time for 8.0.33 but regardless of whether I do, looking at this some more is on my TODO list. Mark > > Cheers, > Ty > > > Case 1 (baseline): > > +-------------+--------------+---------------------------+ > | version | startup time | heap usage after major GC | > +-------------+--------------+---------------------------+ > | tomcat6 | 36,711ms | 21,163,288 | > | tomcat7 | 104,517ms | 489,992,264 | > | tomcat8 | 156,094ms | 1,010,512,568 | > | tomcat8-dev | 139,858ms | 218,976,528 | > +-------------+--------------+---------------------------+ > > > Case 2 (Tomcat 7 and 8 with “jarsToSkip=*”) > > +-------------+--------------+---------------------------+ > | version | startup time | heap usage after major GC | > +-------------+--------------+---------------------------+ > | tomcat6 | 36,711ms | 21,163,288 | > | tomcat7 | 38,979ms | 72,359,840 | > | tomcat8 | 52,040ms | 633,682,336 | > | tomcat8-dev | 66,662ms | 97,365,048 | > +---------+--------------+-------------------------------+ > > > > > On Thu, Feb 18, 2016 at 10:12 AM Ty <ty733...@gmail.com> wrote: > >>> Are you able to build Tomcat 8.0.x from source to test locally or would >>> you like me to provide you with a test build? >> >> Looks like building is pretty straightforward. I'll dive in and post back >> with my testing results. >> >> >> On Thu, Feb 18, 2016 at 9:11 AM Mark Thomas <ma...@apache.org> wrote: >> >>> Another update. >>> >>> Before any fixes, my tests showed a heap of ~1GB with ~30% used by >>> WebappClassLoader and 50% by JarResourceSet >>> >>> The WebappClassLoader issue was triggered by JAR scanning. Disabling / >>> limiting JAR scanning will reduce the impact of this issue. >>> The issue has been fixed in 9.0.x and 8.0.x and will be included in >>> 9.0.0.M4 and 8.0.33 onwards. >>> >>> The JarResourceSet issue was hard coded. There is no way to work around >>> it. This has also been fixed in 9.0.x and 8.0.x and will be included in >>> 9.0.0.M4 and 8.0.33 onwards. >>> >>> Regressions are possible but unlikely. All the unit tests pass and I >>> have been using Atlassian Jira as a test app to check for changes in >>> start time and as a smoke test. There is a small increase in start time >>> with fix for the JarResourceSet issue (~5%) but the reduction in memory >>> usage more than makes up for it. >>> >>> Are you able to build Tomcat 8.0.x from source to test locally or would >>> you like me to provide you with a test build? >>> >>> Looking at the heap dump, there are still a few areas where it may be >>> possible to reclaim more memory. This is on my TODO list and I hope to >>> get to it before the next releases. >>> >>> Mark >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
