I'm using QALoad 5.5.1 Build 195 (Down loading SP4 from Frontline). Conductor scenario as follows
Total 150 Users, spreading accross to 3 Player Machines that comes to 50 Vu's on each player(XP, 3GHz, 1gb RAM) Running a 30 minutes Test makes the health of the Memory and Processor to go above 90% and in turn efects my results. This is ahppening only after upgrading to 5.5.1 with SP4. When running the same scenario in 5.2 was working fine everything was below 50%.
Below are the few changes that I made and checked.
* tried Disabling Expert User
* Tried Process mode - Processor Health was OK but Memory was above 90%
Anybody can give me tips so that I can try and get this resolved.
Re: 5.5.1 with SP4 - Player Machine Health - Not Good
Has anyone had any feed back from Compuware support re this issue. I have several tickets open with support relating to this problem in the last few QALoad builds.
Regardsless of the amount of concurrent users once the conductor reaches a certain level of transactions the cpu hits 100%.
I have tried modify conductor settings and various do_clear options within the script but to no avail.
Re: 5.5.1 with SP4 - Player Machine Health - Not G
I have tried this and disabling heartbeat messages but they make no difference. I have also tried lots of other script modifications suggested by the compuware support helpdesk here in the UK. Its gone all quiet on the helpdesk front now so i think its time to hassle them. I will post a reply on here if i get a resolution but feel that this is a bug in the application.