Hi AlexKaras
When LoadComplete — or more specifically, the Remote Agent Service that is used to generate load — is running a test, it will consume all available CPU resources. (As a side-note, we are looking to change this behavior in the future to be more responsible with CPU resources.) Monitoring the CPU on the machine that is generating the load will not provide a useful metric. To determine load capacity on a local machine, I would be looking to see how the web server responds to all the requests that are generated. In my example above, I determined load capacity by looking at server responses. When the server was overloaded, I started to see HTTP status codes of 500 Internal Server Error.
Does this help?
Hi RyanHeidorn
I've been linked to this conversation as I am evaluating Loadcomplete and saw this behaviour. It was certainly very distracting to see 100% CPU as every other tool on the market works on the assumption that anything above 75-80% CPU has the potential to affect results. For example, you mention that HTTP 500 errors were seen when the load capacity was reached, I would question whether response times were adversely affected before errors were seen?
I am happy to see that this will be resolved though, do you know when this might be implemented?
