If you are doing performance tests on the Stax environment, these should be done on the http://esmecloudperf.esme.staxapps.net environment and not on the http://esmecloudserverapache.DickHirsch.staxapps.net environment.
The esmecloudserverapache is a shared environment and Stax is seeing restarts being triggered by our esmecloudserverapache application. The restarts are happening because of excessive CPU usage. These are triggered anytime an application's load average of a 5 minute period exceeds 90%. In this situation, the application is starving other applications on the servers of CPU time, so corrective measures are automatically taken. Thus, other applications / other Stax customers on the shared server are being affected by our load tests. We have a great relationship with Stax that enables us to have test and performance instances in the cloud and I'd hate it to see detrimentally affected based on our performance tests. I've just set-up the esmecloudperf to use a dedicated server with 1.7 GB Memory - previously we were on a 256 MB shared server- so performance will much better there anyway. So, please just use this instance for our tests. Thanks. Dick
