tag:blogger.com,1999:blog-17332816.post8532651484084026209..comments2023-04-05T22:38:04.960+08:00Comments on Cup(Of T): Tickspiers7http://www.blogger.com/profile/11186470645521299750noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-17332816.post-58335530171714456432010-03-03T07:50:51.438+08:002010-03-03T07:50:51.438+08:00Good question. That's my work PC, a Core 2 Duo...Good question. That's my work PC, a Core 2 Duo @ 3.33 GHz<br /><br />My 2.2 GHz Turion X2 laptop at home only gets 14,288,396, and my HP mini netbook a mere 1,558,642.<br /><br />All these are idle timings, however I didn't think that the stopwatch frequency was affected by CPU clock-rate shifting technologies. Otherwise a stopwatch timing that spanned over a idle/busy period would report completely the wrong duration.<br /><br />So basically: I have no idea. Sure you didn't just drop a digit?piers7https://www.blogger.com/profile/11186470645521299750noreply@blogger.comtag:blogger.com,1999:blog-17332816.post-51206559932142265882010-02-27T07:39:15.085+08:002010-02-27T07:39:15.085+08:00Holy crap, how is your Stopwatch.Frequency so high...Holy crap, how is your Stopwatch.Frequency so high?! Mine is only 2597705, which translates to about 385 ns per tick. I'm on an i7 920 machine, shouldn't it be faster?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-17332816.post-2032052963583657022009-08-05T20:32:09.140+08:002009-08-05T20:32:09.140+08:00Absolutely. My bad. I wonder where I got that idea...Absolutely. My bad. I wonder where I got that idea from.piers7https://www.blogger.com/profile/11186470645521299750noreply@blogger.comtag:blogger.com,1999:blog-17332816.post-57013502901208681672009-08-05T19:17:09.095+08:002009-08-05T19:17:09.095+08:00"Environment.TickCount = 1 ms ticks since pro..."Environment.TickCount = 1 ms ticks since <b>process</b> start"<br /><br />Isn't that supposed to be <i>system</i> start?Recephttps://www.blogger.com/profile/04641390591379888909noreply@blogger.com