On 11/07/2016 09:20, Rainer Jung wrote: > Hi Mark, > > Am 05.07.2016 um 14:27 schrieb Mark Thomas: >> The Gump failures we are seeing are due to the tests taking more than an >> hour to run. I've looked through the logs and I don't see any obvious >> culprits although a second pair of eyes wouldn't hurt. >> >> I've made a few changes to the test configuration to try and speed >> things up (Gump is generally slow and anything I/O related is very slow) >> but early indications are that they won't help. >> >> Suggestions welcome. > > I had a look at the last failure today: > > http://vmgump.apache.org/gump/public/tomcat-8.0.x/tomcat-tc8.0.x-test-nio2/gump_work/build_tomcat-8.0.x_tomcat-tc8.0.x-test-nio2.html > > > When adding the "elapsed" times of the tests run I get 3155 seconds, so > there are 445 seconds which are not accounted by "elapsed". It seems > those are neither in front of the test run (compile, validate) nor is it > the last aborted test. Probably just 1-2 seconds per test which is not > accounted by "elapsed". > > I compared the elapsed times of the individual tests with the ones on my > local (slow) Solaris machine where it takes about 40 minutes to run all > tests for one connector. Here's a comparison showing the delta between > the elapsed times, the slow down in percent, the absolute times for gump > and my system and the test name. The list is sorted by biggest delta > first. I only show the tests that need at least 10 seconds more on Gump > than here on my system: > > 57.772 264.284 92.938 35.166 org.apache.el.TestELInJsp > 55.236 370.301 75.671 20.435 org.apache.jasper.compiler.TestGenerator > 52.894 307.574 78.376 25.482 org.apache.jasper.compiler.TestParser > 40.153 296.155 60.623 20.47 org.apache.jasper.compiler.TestCompiler > 32.692 373.848 44.63 11.938 org.apache.catalina.core.TestApplicationContext > 26.424 227.912 47.082 20.658 org.apache.catalina.startup.TestContextConfig > 25.665 299.34 38.54 12.875 org.apache.catalina.core.TestStandardContext > 24.814 253.752 40.953 16.139 > org.apache.jasper.compiler.TestParserNoStrictWhitespace > 23.946 112.203 220.174 196.228 > org.apache.catalina.authenticator.TestFormAuthenticator > 23.62 222.555 42.893 19.273 org.apache.jasper.compiler.TestValidator > 23.237 413.125 30.658 7.421 > org.apache.jasper.compiler.TestELInterpreterFactory > 23.027 256.913 37.702 14.675 > org.apache.jasper.compiler.TestJspDocumentParser > 21.34 228.608 37.933 16.593 org.apache.catalina.mapper.TestMapperWebapps > 20.872 189.376 44.225 23.353 > org.apache.coyote.http11.TestAbstractHttp11Processor > 20.596 244.28 34.871 14.275 org.apache.catalina.servlets.TestDefaultServlet > 20.332 152.19 59.29 38.958 > org.apache.tomcat.websocket.TestWebSocketFrameClientSSL > 20.085 242.427 34.187 14.102 org.apache.catalina.startup.TestTomcat > 18.141 201.962 35.933 17.792 org.apache.jasper.compiler.TestJspConfig > 18.092 213.287 34.062 15.97 org.apache.catalina.core.TestStandardWrapper > 18.028 210.324 34.369 16.341 > org.apache.tomcat.websocket.TestWebSocketFrameClient > 17.041 262.838 27.506 10.465 org.apache.jasper.servlet.TestJspServlet > 15.26 225.257 27.443 12.183 > org.apache.jasper.tagplugins.jstl.core.TestForEach > 15.175 191.931 31.682 16.507 org.apache.catalina.loader.TestVirtualContext > 14.534 224.755 26.184 11.65 org.apache.jasper.runtime.TestPageContextImpl > 14.476 106.017 255.048 240.572 > org.apache.catalina.startup.TestHostConfigAutomaticDeployment > 14.431 208.782 27.697 13.266 > org.apache.jasper.compiler.TestScriptingVariabler > 13.964 212.477 26.379 12.415 > org.apache.jasper.runtime.TestJspContextWrapper > 13 160.822 34.374 21.374 > org.apache.catalina.core.TestStandardContextResources > 12.444 223.147 22.549 10.105 org.apache.tomcat.util.net.TestSsl > 12.282 229.013 21.802 9.52 org.apache.tomcat.util.net.TestCustomSsl > 12.054 200.033 24.104 12.05 org.apache.jasper.TestJspCompilationContext > 11.905 226.259 21.334 9.429 org.apache.jasper.runtime.TestJspWriterImpl > 11.244 204.508 22.003 10.759 org.apache.jasper.servlet.TestTldScanner > 11.126 169.429 27.151 16.025 org.apache.naming.resources.TestWarDirContext > 10.714 211.989 20.281 9.567 org.apache.naming.resources.TestNamingContext > 10.676 257.696 17.446 6.77 org.apache.catalina.mapper.TestMapperListener > 10.517 177.852 24.026 13.509 org.apache.jasper.tagplugins.jstl.core.TestSet > 10.156 202.369 20.077 9.921 org.apache.jasper.runtime.TestCustomHttpJspPage > 10.039 205.175 19.584 9.545 javax.el.TestCompositeELResolver > 10.033 223.574 18.152 8.119 javax.servlet.jsp.TestPageContext > > Maybe the list gives an idea, whether it is more an I/O or CPU shortage > or something else?
Thanks. That suggests that I/O constraints are more significant than CPU which is what I know to be the case for the VM currently hosting Gump. Gump is about to move VMs which should help. There is also scope to reduce the I/O associated with JSP compilation. Currently each file is read multiple times. I'll add a BZ entry for that so it doesn't get lost. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
