Hi, Is the fix an added option? What is the default?
In the coming weeks we will try to test it at our client's site and post the results. Thank you! Andrej On 2010/11/28, at 3:51, sebb <[email protected]> wrote: > On 27 November 2010 18:50, sebb <[email protected]> wrote: >> On 20 November 2010 11:32, sebb <[email protected]> wrote: >>> On 20 November 2010 11:28, Andrej van der Zee <[email protected]> >>> wrote: >>>> Hi, >>>> >>>> >>>>> >>>>> Nanotime was added to try and provide additional resolution - looks >>>>> like it causes more problems than it solves... >>>> >>>> Is this recently added? Are there older JMeter versions that use >>>> currentTimeMillis only? >>> >>> Only very old ones. >>> >>>>> >>>>> I think the options are: >>>>> >>>>> currentTimeMillis only >>>>> Use cTM for start (or end) timestamp, and use differential nanoTime for >>>>> elapsed. >>>>> >>>>> The second option is as at present, but without storing the fixed base >>>>> time. >>>>> There cannot then be any accumulation of drift. >>>>> >>>> >>>> Would solve our problems. >>> >>> I'll try and get a nightly build out soon. >> >> Builds after r1037933 have the fix. > > Oops - I meant builds from (and including) r1037933 have the fix. > >>>> Cheers, >>>> Andrej >>>> >>>> --------------------------------------------------------------------- >>>> 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
