Re[6]: [GD-Windows] Performance timing

[Carl B. <car...@ya...>]

OK, so what I'm getting is that while GetTickCount has an exceptionally fast execution time, it's not as precise (by quite a bit) as RDTSC or QueryPerformanceCounter.  Of the latter two, RDTSC is generally faster.  So if I could only pick one for general use, I'd pick RDTSC.  Although the most reliable solution is to use more than one and have them "vote".

------------------------------------------
Wednesday, February 11, 2004, 9:16:09 AM, you wrote:

> (To be more precise, it does a fixed-point multiply and shift to convert the
> count to milliseconds.)

> -----Original Message-----
> From: Donavon Keithley 
> Sent: Wednesday, February 11, 2004 11:02 AM
> To: 'gam...@li...'
> Subject: RE: Re[4]: [GD-Windows] Performance timing


> GetTickCount is just a tiny function that reads a variable that's
> incremented in the system timer interrupt handler.  In situations where this
> timer is useful, the extra speed is insignificant.


> -----Original Message-----
> From: Carl Bevil [mailto:car...@ya...]
> Sent: Tuesday, February 10, 2004 7:27 PM
> To: Simon O'Connor
> Subject: Re[4]: [GD-Windows] Performance timing


> Did that, and they have a nice utility that performs some timing tests on
> your machine and spits out a report (it's at
> http://developer.nvidia.com/object/timer_function_performance.html).

> The report had interesting results: