Re: time.clock() going backwards??
On 2006-08-28, Grant Edwards <grante@visi.co mwrote:
>
>
This is
Oops. Hit the wrong key. I meant to say:
This is a _Microsoft_Prod uct_. There doesn't have to be a
reason for something to be done in a half-assed manner.
Yup.
--
Grant Edwards grante Yow! People humiliating
at a salami!
visi.com
On 2006-08-28, Grant Edwards <grante@visi.co mwrote:
>>For processors that run at (say) 2GHz, several million (say 10
>>million) represents a difference of 10e6/2e9 = 0.005 seconds
>>between when the processors were sufficiently powered up to
>>start counting cycles.
>>million) represents a difference of 10e6/2e9 = 0.005 seconds
>>between when the processors were sufficiently powered up to
>>start counting cycles.
>If it were so, than why can't the delta of time between the
>processors be set to exact zero?
>processors be set to exact zero?
This is
This is a _Microsoft_Prod uct_. There doesn't have to be a
reason for something to be done in a half-assed manner.
>I assume, that it is known how many cycles adjusting the value
>will take, so it could be done exactly
>will take, so it could be done exactly
--
Grant Edwards grante Yow! People humiliating
at a salami!
visi.com
Comment