Click here to Skip to main content
Click here to Skip to main content

The CPerfTimer timer class

, 27 Apr 2000
Rate this:
Please Sign up or sign in to vote.
This class encapsulates QueryPerformanceCounter for high precision timing
  • Download source files - 3 Kb
  • Updated: the class is now thread safe.

    High resolution timing is supported in Win32 by the QueryPerformanceCounter and QueryPerformanceFrequency API calls. The timer resolution varies with the processor. Today's high speed processors have a timer resolution of less than a microsecond. Of course, this is a much better resolution than the GetTickCount API!

    Using the QueryPerformanceCounter calls directly takes too much typing and the resulting code is usually hard to read. So, I looked all over the net for a timer class but I could not find one that suited me. I wrote a simple and powerful timer class and named it CPerfTimer. I wrote this a long time ago but I still have not had the need to update it. Searching the net I could not find a timer class as simple to use and as useful as CPerfTimer. Several other timer classes are available and they vary as to their simplicity and usefulness. I do not claim that this is the end-all-be-all of timer classes; but, I hope that someone will find it useful enough to refrain from taking the time to write yet another timer class.

    This class is simple to use. Just declare a variable as type CPerfTimer, call Start() to start timing and call Stop() to stop timing. You can pause a timer by calling Stop() and then you can call Start() to resume. Retrieve the elapsed time by calling an Elapsed...() function. Assignment, addition, subtraction and comparison are supported. There are a few information calls available also. All calls except Start and Stop can be performed on a timer without stopping it.

    I have not included separate documentation or example application. The code is fairly well documented and the above paragraph was copied from the CPerfTimer.h file. Methods for adding, subtracting and comparing CPerfTimers and seconds (double) are also included. And, a CPerfTimerT class that should be thread safe (no extensive testing has been done). Please inform me if any bugs are found or you have an idea for an enhancement.


    This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

    A list of licenses authors might use can be found here


    About the Author

    Dean Wyant
    Web Developer
    United States United States
    No Biography provided

    Comments and Discussions

    QuestionError Message ?? PinmemberAnonymous18-Mar-02 8:58 
    AnswerRe: Error Message ?? PinmemberDean Wyant21-Mar-02 5:34 
    Generalexample please PinmemberRamy8-Dec-01 21:05 
    GeneralRe: example please PinmemberDean Wyant9-Dec-01 10:38 
    GeneralRe: example please PinmemberRamy10-Dec-01 17:06 
    GeneralTimer runs to quick PinmemberRob Ottenhoff5-Mar-01 1:01 
    GeneralRe: Timer runs to quick PinmemberAnonymous5-Mar-01 7:04 
    GeneralUsage Notes PinmemberDean27-Jan-01 12:15 
    Several people have contacted me stating that they get inconsistent results. Results can be inconsistent for several reasons.
    1. Program is compiled for debugging. The program itself does not run consistently due to debug code and task switching. Only expect consistent results in release compiled code. In debug code, the first run of the timer may seem excessive due to the operation of the debug code. Subsequent runs may be more consistent. Of course, the times are correct, it is the operation of the program that is inconsistent.
    2. Task switching. Your code that is being timed can be interupted for a task switch. The time will reflect the true time which includes the time the other thread runs. This is unavoidable in a multi-threaded operating system. Some control may be gained by placing Sleep(0) in your code right before starting the timer. Sleep(0) will reset your threads time slice and make it more likely that your timed operation will not be interupted. Of course, if your operation takes more than one time slice, it will still get interupted. The priority of the thread affects task switching also. These are issues we have to deal with when running on a multi-thread OS. We have to remember that we are sharing the processor and the OS controls how much time we get. If anyone knows any other Win32 calls that may help control task switching, please let me know or post them here.
    3. Very short operations (< 1us?) cannot be timed accurately due to CPerfTimers overhead and resolution. Any operation that is shorter than the time it takes to Start and Stop the timer cannot be timed accurately. For instance, if you put the timer inside a tight loop, you may be trying to time an operation that is less than the timers resolution. The result will be 0.
    This class is reliable and accurate because QueryPerformanceCounter is. Basically, it is like placing the QueryPerformanceCounter etc. calls right in your code. CPerftimer is just much easier to use then the direct calls.
    If anyone finds anything wrong with the class, please let me know.

    GeneralVery useful... Pinsusskabir5-Sep-00 1:37 
    GeneralThe poor rating was due to compile problem - update should be posted soon PinsussDean Wyant14-Apr-00 23:44 
    GeneralUpdated posted PinsussChris Maunder14-Apr-00 23:50 

    General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

    Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

    | Advertise | Privacy | Terms of Use | Mobile
    Web03 | 2.8.150224.1 | Last Updated 28 Apr 2000
    Article Copyright 2000 by Dean Wyant
    Everything else Copyright © CodeProject, 1999-2015
    Layout: fixed | fluid