Performance Issues

...

	Reasons	Solutions
Download, unzip, build war and deploy to cargo	Requires many filesystem I/O but not network I/O because of local cache of zip files	To be defined. Publishing a standalone and runnable WAR is a good candidate.
Server startup	See above
Server shutdown	Timeout to guarantee that queue of notifications is empty	See https://jira.codehaus.org/browse/SONAR-3509
Initialization of Selenium RC	Is the Selenium proxy long to be started ? To be verified	Test suites could use the same Selenium RC proxy http://jira.sonarsource.com/browse/ORCH-91
Too many server startups	Each Java file uses at least one server	Group unit tests by reusing shared servers. BUT this is a problem only if server startup is long.
Project inspections are long		Use Java Runner instead of Maven to launch inspections Do not build sources when possible, by storing bytecode in SCM Do not execute rule engines when not needed -> should be the default behavior
Each junit test is long	Due to test requirements (server, code inspection, selenium rc)	Use parallel tests

UI

TO BE DEFINED

	Solutions
Many HTTP requests to get images	Use CSS sprites