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.....
-Mike On Fri, 2002-04-26 at 16:43, Kate Rosenbloom wrote: > Looks like overkill. Distinguishing threads from earlier runs in old > results files > might be better done with a result file post-processing step. > > Kate > > "Stover, Michael" wrote: > > > > Some ideas on making unique names: > > 1. use the ThreadGroup name, not "JMeterThread". Or both. > > 2. Number each thread in the ThreadGroup 1...N > > 3. Create a unique identifier number, based on current time stamp (in > > milliseconds), host ip, and a 128-bit random number. > > > > Make a string from all these parts, example: "JMeterThread-Test Group > > 1-5-329832845092375487932479795893923" > > It's kinda big, but it has everything for everyone, splittable on "-" (or > > some other agreed upon char). > > > > If anyone knows an easier way, speak up. > > > > -Mike > > -- > 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]>
