Opened 15 years ago

Last modified 15 years ago

#2 new enhancement

Inefficient Timer Class

Reported by: Christoph Mayer Owned by: stud-veber
Priority: minor Milestone:
Component: Utility Version: 0.1.0
Keywords: timer Cc:

Description (last modified by Christoph Mayer)

The Timer class currently opens up one thread for each timer and therewith creates unnecessary resource overhead. Surely, this can be done more efficiently. There are two options to tackle the problem:

  1. Use native timer functionality from the OS
  2. Use the SystemQueue with time-sorted ordering and only one interruptable timer that always times the nearest timer. The SystemQueue class has already some internals for this. As timer callbacks need synchronization with the SystemQueue anyways, this would be a nice and clean solution. But certainly tricky to achieve with good performance.

Change History (3)

comment:1 by Christoph Mayer, 15 years ago

Type: defectenhancement

comment:2 by Christoph Mayer, 15 years ago

Description: modified (diff)
Owner: changed from somebody to stud-veber
Note: See TracTickets for help on using tickets.