it goes like this: request#1 - sent at 0ms request#1 takes 400ms to complete request#2 - sent at 700ms (400 + 300) request#2 takes 200ms to complete request#3 - sent at 1200ms (700 + 200 + 300) etc.....
-Mike > -----Original Message----- > From: Michael Morris [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 27, 2001 10:23 AM > To: '[EMAIL PROTECTED]' > Subject: single thread testing - how exactly does it work? > > > Hi all, > > I wonder if you could help me. I am trying to test a site > using a single > thread with a time delay of 300ms. My question is this. Does this a) > actually send a request every 300ms or b) simulate a single > thread every > 300ms. > > If a) then surely that would mean that say I send a request > at time t=0ms > the first response takes 400ms the second request would be > delayed by 100ms, > say this request now takes exactly 500ms, surely that would > mean that at > time t=900ms two threads should be sent simultaneously - what > happens now? > > Alternatively, if b) then we would expect a request to be > sent every 300ms > no matter what the response times are, therefore many threads > are actually > used. > > Of course the answer could be c) none of the above. > > I hope that this question is clearer than I think! > > thanks, > > Michael > > > -- > 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]>
