Thanks for the suggestion. It might be a good paragraph for the docs. In
case anyone else needs to do a similar thing, here's a pretty
straightforward way:
On each of your remote JMeter servers, add a command-line parameter
like: -JserverNumber=0 and increase the number on each subsequent JMeter
server.
Then, define your number of threads as a configuration parameter in your
Test Plan element:
threadCount = 50
Also, you may want to start at a user number greater than zero (we have
to since each run modifies the data set and it takes a long time to run
a script to reset it, so it's easier to increase the first user number
for each subsequent run):
firstUserNumber = 1000
Reference it in your thread group (e.g. Number of Threads =
${threadCount}).
Then the username variable you need to use to iterate through you can
use something like this (split at commas for readability):
USER_PREFIX_${__intSum(${firstUserNumber},
-1,
${__javaScript(${__P(serverNumber)}*${threadCount})},
${__counter(FALSE,uid)},dddd)}
The -1 is because the counter appears to start at 1. Of course, you
would probably have to modify this slightly for multiple thread groups
running simultaneously. I'm not sure if this is necessarily the best
way, but it worked for me.
-Keith Zantow
> -----Original Message-----
> From: Erik Nizenkoff (enizenko) [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 20, 2007 2:07 PM
> To: JMeter Users List
> Subject: RE: Distributed test variables
>
> What I have been doing to test user numbers in sequence is to start
the
> counter with a property value.
> Then I set the property from each server when I start it. Such as
> Juser_counter=1000
>
> -Erik Nizenkoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
