> I am thinking I'd include an option to just simply "synchronize on this
> timer".  That way, there's an option that allows you to just say all
> threads should wait till all get to this point before proceeding.  I
> agree times are iffy and I couldn't think of much use for that myself.
> But a generic sync point could be useful and simple to use.

Sometimes the most obvious solutions are hidden... ;-)

Thanks, Leo

> -Mike
> 
> On Thu, 2005-02-24 at 15:44 +0100, Leo Leo wrote:
> > 
> > 
> > That would be perfect. I thought about creating such a component
> > myself, but
> > since I am no java-developer ==> :(
> > 
> > > 
> > > However, with the Thread Group, I feel like we have discovered that
> > > absolute times are not the most useful thing to use in JMeter.
> > Relative
> > > times seem better - ie a delay that delays until a certain amount of
> > > time has passed since the test started.  
> > > 
> > > Of course, I would do both options in this timer.  Really would be
> > very
> > > simple.  Do you think that would meet your needs?
> > 
> > The good way would be, if it is possilbe to read such a value from a
> > file
> > (with the _StringFromFile-function).
> > 
> > But I see a more general problem: If you run in loops, the check will
> > be
> > done only once. So you would need an absolute timestamp for all
> > threads
> > which is valid for each loop iteration.
> > 
> > Maybe the following approach could work:
> > - a parameter which handles the start-timestamp relative/absolute to
> > teststart
> > - a second parameter which handles start-timestamp for each loop
> > iteration
> > (Either by Thread-Group or Logic Controllers) 
> > 
> > Example:
> >    Wait a maximum of 10 minutes after teststart
> >    Wait a maximum of 3 Minutes after the last iteration over itself
> > (the
> > Synchronize-Component)
> > 
> > All threads, which came after the timestamp to this Component:
> >  a) Pass
> >  b) eventually handling by assertion (but I think that would be more
> > difficult to implement)
> > 
> > I think the overall problem will be to determine the amount of time,
> > which
> > have to pass since the last iteration (or test-start), but since one
> > has the
> > time to wait, until all threads are settled, the performance in this
> > time is
> > not relevant, so you can set these waiting-times long enough.
> > 
> > Thank you very much,
> > Leo
> > 
> > 
> > 
> > -- 
> > Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
> > GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail
> > 
> > ---------------------------------------------------------------------
> > 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]
> 

-- 
Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to