[
https://issues.apache.org/jira/browse/DISPATCH-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800983#comment-16800983
]
Alan Conway commented on DISPATCH-1274:
---------------------------------------
The issue this patch was aiming at is a set of often-called code points that
*always* pass a literal 0 to schedule() just to put work on other threads.
Those uses don't need a timed delay, just a thread-safe work queue. The
overhead of clock_time() and a sorted schedule is always wasted for those
calls. For code that actually is trying to set up a timed delay, I think the
existing timers are fine - even if the delay sometimes happens to be 0.
> Optimize qd_timer_schedule(0)
> ------------------------------
>
> Key: DISPATCH-1274
> URL: https://issues.apache.org/jira/browse/DISPATCH-1274
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Affects Versions: 1.5.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Major
>
> qd_timer_schedule() uses the general timeout mechanisms which includes
> checking system time (on schedule and on PN_PROACTOR_TIMEOUT wakeup) and
> adding/removing work items from sorted list. Optimize the schedule(0) case as
> a simple work_list using pn_proactor_interrupt() for wakeups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
