On Fri, Oct 26, 2007 at 02:20:15PM +0000, Andrew J. Savory wrote: > Hi, > > We're seeing some performance issues with a deployment of Hippo, so I've been > trying various things to quantify the problem prior to trying to solve it. > > One thing I've done is to put together some JMeter tests, which I thought > might be of use to others wishing to test their CMS deployments. I've > attached the test script. > > What does this do? It loads the login page, then posts the login form back to > the server, then loads the initial dashboard logged-in view, then logs out > again. You can see the performance of loading the initial login screen by > clicking on 'Graph results' under 'Login'; you can see the performance of > loading the dashboard by clicking on 'Graph results' under 'Dashboard'. >
I've not tried your script, but we have a similar JMeter test script, which came into being because of an issue reported to us. I'm not familiar (as I haven't ran your script) with the behaviour as reported by your script, maybe you can elaborate, but we've seen the following; Initially the performance is acceptable, but a number of runs it becomes slow and, depending on the application server used, actually fails. The problem is dat when logging out, you the CMS returns you to the login screen again. This in fact opens up a new session (not just a new JSESSION id, but also a new continuation script id from Cocoon). So in the final step of a single JMeter script there is a dangling session around and per thread in the next iteration. If you have 30 threads, each doing 100 iterations, you will end up with 3000 dangling sessions, which will take a long time to time-out. This is simply not a fair test, as either the person would log in using the same session again, or there would be that many login-logouts per second. As a workaround, it is possible with the most up-to-date CMS to put a distinct logout splash screen, such that a new session/continuation wouldn't be generated on logout. \Berry -- Berry A.W. van Halderen [EMAIL PROTECTED] / [EMAIL PROTECTED] Disclaimer: the above is the author's personal opinion and is not the opinion or policy of his employer or of the little green men that have been following him all day. ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
