| Field |
Value |
| Bugzilla ID |
3706 |
| Reporter |
Carlos O'Ryan |
| Assigned to |
Carlos O'Ryan |
| Product |
ACE |
| Component |
ACE Core |
| Version |
5.7.0 |
| Platform / OS |
All / All |
| Priority |
P3 |
| Severity |
normal |
| Status |
RESOLVED |
| Resolution |
FIXED |
| Created |
2009-06-24 08:39:03 -0500 |
Originally posted by Carlos O'Ryan on 2009-06-24 08:39:03 -0500
The locking strategy for the ACE reactor timer queues is decided at compile-time. See ace/Timer_Queue.h. However, some applications use the ACE reactor with and without locks, depending on the application. TAO even offers run-time options to select the type of reactor, and its performance tests demonstrate significant improvements because of this.
We will propose a number of changes to the timer queues to allow run-time selection of the lock type.
This will require a number of changes to the class structure for ACE_Timer_Queue<>. But at the end, applications will be able to select the type of queue and the type of locking they want for their application.
Originally posted by Carlos O'Ryan on 2009-06-24 08:39:03 -0500
The locking strategy for the ACE reactor timer queues is decided at compile-time. See ace/Timer_Queue.h. However, some applications use the ACE reactor with and without locks, depending on the application. TAO even offers run-time options to select the type of reactor, and its performance tests demonstrate significant improvements because of this.
We will propose a number of changes to the timer queues to allow run-time selection of the lock type.
This will require a number of changes to the class structure for ACE_Timer_Queue<>. But at the end, applications will be able to select the type of queue and the type of locking they want for their application.