I doubt there will be any collisions given that the number includes current timestamp and host ip.
My idea behind guaranteeing uniqueness is to allow for a scenario such as: I have 6 thread groups and I've got 6 saved results files. At some later point, I want to see all the results in one visualizer, however, and I want all results to be ordered correctly by time. Thus, JMeter will have to combine 6 files of sample results, and keep each thread distinct. -Mike -----Original Message----- From: Martin Ramshaw [mailto:[EMAIL PROTECTED]] Sent: Friday, April 26, 2002 3:26 PM To: JMeter Developers Subject: RE: Thread Numbering (was Re: IRC) >Some ideas on making unique names: >1. use the ThreadGroup name, not "JMeterThread". Or both. The ThreadGroup name makes more sense, as it probably carries more information. >2. Number each thread in the ThreadGroup 1...N Agreed. >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). Sounds good to me. I'm not sure what the random number contributes, though. If it is to preserve the uniqueness of the test results, they will probably collide at some extremely unlikely conjuncture. Perhaps it might be better to allow for thread-numbering to start after the last previously used thread (i.e. N + 1) ? Regards -- 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]>
