An Overlay-based
Virtual Network Substrate
SpoVNet

Ticket #2 (new enhancement)

Opened 3 years ago

Last modified 3 years ago

Inefficient Timer Class

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

Description (last modified by mayer) (diff)

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

Changed 3 years ago by mayer

  • type changed from defect to enhancement

Changed 3 years ago by mayer

  • owner changed from somebody to stud-veber
  • description modified (diff)

Changed 3 years ago by stud-veber

Note: See TracTickets for help on using tickets.