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. To use it, you'll need a copy of Apache JMeter [1], and you'll probably need to change the default configurations: * in 'HTTP Request Defaults', make sure the server name, port number and protocol are correct * in 'HTTP Header Manager', make sure your User-Agent string matches the browser deployed at your organisation * in 'Send login details', make sure the username and password are correct * in 'Hammer Hippo', tweak the number of threads and number of loops (the default of 5 users and 50 loops = 250 results) To run, select 'Run', 'Clear all'; then 'Run', 'Start'. 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'. It's generally best to run JMeter on a box other than the cms server. Beware of external factors impacting your results, such as network congestion or other users hammering the server. In case you're interested, on this box the login page currently loads in ~ 695 ms and the dashboard loads in ~ 9 agonising seconds. How about yours? [1] http://jakarta.apache.org/jmeter/ Thanks, Andrew. -- Andrew Savory Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 Sourcesense - making sense of Open Source: http://www.sourcesense.com
HippoCMS.jmx
Description: Binary data
******************************************** Hippocms-dev: Hippo CMS development public mailinglist
