On 08/05/06, sebb <[EMAIL PROTECTED]> wrote:
On 08/05/06, Bennett McElwee <[EMAIL PROTECTED]> wrote: > My results file seems to show a single thread making two simultaneous > requests. This seems to indicate that JMeter is generating bad results. > I wonder if anybody else has seen this? > > The following lines appeared in my CSV file for a test. (There were 50 > threads total; I have omitted intervening lines for other threads.) > > timeStamp,time,label,responseCode,responseMessage,threadName,dataType,su > ccess,failureMessage > 1147052818441,360118,Page One,Non HTTP response code,Non HTTP response > message,Thread Group 1-1,text,false,Test failed, text expected to > contain /Testing/ > ... > 1147052854550,72124,Page Two,Non HTTP response code,Non HTTP response > message,Thread Group 1-1,text,false,Test failed, text expected to > contain /Testing/ > > > The second request was apparently initiated at time 1147052854550 - > 72124 = 1147052782426. But this is before the first request finished.
On second thoughts, I think not ... Assuming that the timeStamps are END times, we have: Req: EndTime Elapsed StartTime 1 114705281844 1360118 1147052458323 2 1147052854550 72124 1147052782426 And: 1147052782426 > 114705281844 i.e. the start time of the second request is later than the end-time of the first. The default timeStamp of the END time is very confusing, which is why the default will change in the next release. It can be changed in 2.1.1 - see jmeter.properties. S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
