HomeSUPPORT QUESTIONS

Need help with StresStimulus? Start here.

Emulating different VU credentials on agents Messages in this topic - RSS

Unregistered User
Unregistered User
Posts: 162


2/22/2013
Unregistered User
Unregistered User
Posts: 162
We have an enterprise license of stress stimulus.  We are attempting to stress test an application through a load balancer.  The load balancer has source address affinity on, so we set up a number agents up so the address would be different.  We recorded some tests and parameterized the users and passwords.  Our  application locks out users if they are already logged on via a different computer.  The problem is, Stress Stimulus is using the same users on every agent computer. 
For example:
We have a test 100 virtual users in a steady load and 4 testing agents.  I would expect that the parameters for the first 25 VUs would be sent to the first agent, the second set of 25 VUs would be sent second agent, and so on..   What we are seeing is the first set of 25 VU parameters are being sent to all 4 agents, rendering our test invalid because 75% of the VUs are locked out. 
Is there any way around this? Can we send the first 25 rows of our data set to the first agent, the second set to the second agent, and so on?
Thanks!


0 link
Vadim @StresStimulus
Vadim @StresStimulus
Administrator
Posts: 583


2/22/2013
Vadim @StresStimulus
Vadim @StresStimulus
Administrator
Posts: 583
Here is how to implement different datasets  with credentials or other information on the Agents.
When you start a test, StresStimulus controller copies the.csv file with 100 user credentials to each of your four agents. The file is stored in one of these folders:

  • %My Documents%\Fiddler2\StresStimulus\AgentTemp\span class="GINGER_SOFATWARE_noSuggestion GINGER_SOFATWARE_correct">testName>_span class="GINGER_SOFATWARE_correct">RandomNumber>\span class="GINGER_SOFATWARE_noSuggestion GINGER_SOFATWARE_correct">testName>\

  • C:\Windows\System32\Fiddler2\StresStimulus\AgentTemp\<testName>_<RandomNumber>\<testName>\


Everything utility available here, simplifies search of the csv files.

After that, each of four agents start the test using the same .csv file. At this point, you need to abort the test,  edit each of the agent's .csv files to remove the unnecessary dataset rows, and then launch the test again.  Keep in mind, that after changing the  .csv file on the controller, all  your changes in the agents'  .csv files will be overwritten  because of the version control. Any other changes in the test will not override the .csv files.

Update: if you use v 3.0 and use  VU-Bound or random databinding method, then this workaround is not required, as StresStimulus should handle this situation correctly.
0 link






Copyright © 2017 Stimulus Technology