If your test script will run in only 1 machine (not distributed), ZK
solution works great.
If you intend to distribute your test among many slaves you could define a
distinct property value (m1, m2, m3, ...) for each JMeter slave
initialization command.
In a distributed environment your username should be
"username${count}${myProp}" or "username${__threadNum()}${myProp}"
If you don't want to define a distinct property value for each JMeter slave
you could use ${__machineName()} function (
"username${count}${__machineName()}" or
"username${__threadNum()}${__machineName()}" ).
This will only work if all JMeter slaves are running on different machines.
2013/9/23 ZK <[email protected]>
> Hi,
> try adding a "counter" to your test and create a new user with:
> userName${counter}
>
>
> ZK
>
>
>
> --
> View this message in context:
> http://jmeter.512774.n5.nabble.com/Creating-5000-users-with-simmilar-user-name-tp5718195p5718223.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
