Has anyone else experienced the duration element in the scheduler being very inaccurate? Example, I have a plan with one threadgroup that started at a specific time and with a duration of 3600 seconds (one hour). The test ended normally, but only 28 actual minutes elapsed. The scheduler appears to start accurately based on my system's clock. But the duration element appears not use the system clock and it seems to be using its own inaccurate mechanism. I have official version 2.0.1
Here was my plan setup: Threadgroup: Threads= 1, loopcount=1, rampup=1, Scheduler start time 2004/07/29 10:00:00 duration: 3600 -once only controller -sample1 -loop controller: infinite -uniform random timer: 5000ms constant, 10000ms random -sample2 -sample3 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
