But, where are you getting the user information from? JMeter doesn't
require unique users per thread, and I think it would be a huge pain for
those who didn't care about such things if you started requiring it. Who
wants to load 50 users into their web app and then into JMeter just to get a
quick idea of how their application performs under stress?
The ${thread-group}-${thread-num} gives uniqueness for any given
"start-stop" sequence, and then each sequence can be given a unique number
to differentiate it from any other sequence.
-Mike
-----Original Message-----
From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 29, 2002 9:15 AM
To: JMeter Developers List
Subject: Re: Thread Numbering (was Re: IRC)
mike wrote:
> It's true, the uniqueness information doesn't need to be part of the
> thread name - it could be something stored separately. I know just the
> place, given the work I've done so far.....
>
Thread name uniqueness does help for certain things:
* Distinguishing which user is being tested.
* Debugging the test
* Debugging JMeter.
For that reason, I suggest the very simple naming policy:
${thread-group}-${thread-num}-${userid}
+---------------------------+ +-------+
Debug Information User Info
Very simple, and everything we need to know is documented.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
