Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Windows Timing performance

Windows Timing performance

Scheduled Pinned Locked Moved C / C++ / MFC
performancequestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    Geert Craessaerts
    wrote on last edited by
    #1

    Hi, I've written a program to test the performances of a windows timer under different work loads. In a first step we used the program under a windows 98 platform with a timer frequency of 5Hz. So every 200msec the Wintimer should sent a WM-TIME message to the OnTimer function. Because the timer tick frequency of a windows 98 platform is about 18Hz(55msec) there will be approximately a time delay of 20msec. When I start the program with no work load(0 floating point operations) the time delay is also 20 msec, so everything is normal. But when I want to increase the work load to 1.000.000 floating point operations the time delay becomes smaller. I would expect that it would increase with increasing work load! Can anyone explain this? Kind regards, Geert

    J 1 Reply Last reply
    0
    • G Geert Craessaerts

      Hi, I've written a program to test the performances of a windows timer under different work loads. In a first step we used the program under a windows 98 platform with a timer frequency of 5Hz. So every 200msec the Wintimer should sent a WM-TIME message to the OnTimer function. Because the timer tick frequency of a windows 98 platform is about 18Hz(55msec) there will be approximately a time delay of 20msec. When I start the program with no work load(0 floating point operations) the time delay is also 20 msec, so everything is normal. But when I want to increase the work load to 1.000.000 floating point operations the time delay becomes smaller. I would expect that it would increase with increasing work load! Can anyone explain this? Kind regards, Geert

      J Offline
      J Offline
      Joel Lucsy
      wrote on last edited by
      #2

      My semi-educated guess: that your program is getting more scheduled time and can therefore respond quicker to the WM_TIMER message. My guess is that if there was another program consuming more CPU than yours, you might take longer to respond. Joel Lucsy (jjlucsy@concentric.net)

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups