| || |
QALoad Player Agent CPU Maxed
I have a run a load with 20 users against a test environment and when I do so the agents cpu usage maxes out and holds. When I run the same test against our prod site and others, this does not occur. The script just hits the home page and nothing else. My question is, what ip is being used in the test, the agent or the conductor? We put a sniffer on it and the conductor's ip showed up.
Re: QALoad Player Agent CPU Maxed
**Note - I have never used QALoad**
That doesn't make any sense. If the load is being generated by an agent, it is the agent's IP that the sever is seeing. The controller "pushes" the scripts to the agent during initialization, then may or may not continue active communication during the test execution, but if there is any, it will be minimal just to coordinate times. After the test execution completes, then the data collected is passed back from the agent(s) to the controller for processing. (unless QALoad handles agents differently than EVERY other load generation tool I have ever touched)
If the agent pegs on scripts, but the controller doesn't peg on those same scripts, my questions are these.
1) have you looked at the RAM on either/both?
2) have you run other scripts on the agent without problems?
3) are you certain the controller and agent are configured correctly?
4) what happens if you execute a single user test via the agent?
Scott Barber, Sr. Performance Engineer