On 18/02/2016 00:26, Ty wrote: >>> For Ty's purposes, simply avoid JAR scanning entirely should eliminate >>> the heap issues, right? Moving from Tomcat 6 means that JAR scanning >>> is not required for correct operation of their application. > >> Yes. http://wiki.apache.org/tomcat/HowTo/FasterStartUp has the details >> of the configuration required. > > I might be missing something, if so please correct me, but it seems that > there's a huge difference with Tomcat 8, even when JAR scanning is taken > out of the picture (jarsToSkip=*). > > For my test case, Tomcat 8 has a heap size of ~1GB with JAR scanning > enabled, and ~600MB with jarsToSkip=*. That's a 40% improvement by > disabling JAR scanning, sure, but for comparison, same test case, Tomcat > 6's heap is ~20MB while Tomcat 7's (with jarsToSkip=*) is ~70MB. We're > still back to a 30x increase in heap utilization from Tomcat 6 to Tomcat 8, > and a 10x increase from Tomcat 7 to Tomcat 8, without having JAR scanning > in the mix.
Sorry. Not enough sleep when I wrote that. The WebappClassLoader issue is addressed by disabling JAR scanning but the JarResourceSet issue is not. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
