[
https://issues.apache.org/jira/browse/DISPATCH-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462775#comment-17462775
]
ASF subversion and git services commented on DISPATCH-2298:
-----------------------------------------------------------
Commit 6feb25e833768c41ea7cd6c17f2c61fe362aa4b8 in qpid-dispatch's branch
refs/heads/main from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=6feb25e ]
DISPATCH-2298: Avoid rescheduling qd_timer if we are already servicing timer
If we are in the middle of running through the list of timers in
qd_timer_visit() we don't need to wake the timer as anything we add to
the list will get serviced immediately in any case.
> Eliminate some unnecessary uses of pn_proactor_set_timeout
> ----------------------------------------------------------
>
> Key: DISPATCH-2298
> URL: https://issues.apache.org/jira/browse/DISPATCH-2298
> Project: Qpid Dispatch
> Issue Type: Improvement
> Reporter: Andrew Stitcher
> Priority: Major
>
> Currently qp_timer_schedule() always calls qd_server_timeout() to wake up the
> timer callback handler even if the handler is already running. This causes
> unnecessary system calls in pn_proactor_set_timeout(). If the
> qp_timer_visit() loop is already running then we are guaranteed that the
> newly scheduled timer will be noticed by the loop without having to wake the
> loop up.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
