Just a suggestion, it still won't be easy: - test machines with synchronized clocks (look at about time in case of winodws, similar tools in case of other OS); - synchronizing of the threads occurs at certain intervals; - use beanshell to control this... itl won't be pretty, though. Maybe there are easier ways to achieve what you want to test, I doubt that it is strictly necessary to syncronize all threads on all machines.
On Mon, Sep 13, 2010 at 6:03 PM, sebb <[email protected]> wrote: > On 13 September 2010 15:30, Jens Müller <[email protected]> wrote: > > > > Hi, > > > > I have not set up a test case to proof it but if I look at the structure > of JMeter, it seems to me the synchronizing timer does not work in > distributed mode meaning it does not block all threads throughout all agents > executing the test until they have joined, but only those on the respective > local machine - right? > > Each server runs the test plan independently. > > > If this is indeed the case, how could a distributed sync timer be > implemented? > > No idea. Probably quite tricky. > > > Regards, > > Jens > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
