[
https://issues.apache.org/jira/browse/DISPATCH-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418792#comment-17418792
]
ASF subversion and git services commented on DISPATCH-1274:
-----------------------------------------------------------
Commit bf1359829afbf126ad5dc0dd6bf76ebf34f08bac in qpid-dispatch's branch
refs/heads/main from Ken Giusti
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=bf13598 ]
DISPATCH-1274: avoid sharing mutex between timer and server
Historically the qd_server_t and the timer subsystem have shared a
single mutex. There is no technical reason for this as each use the
lock to protect entirely separate critial sections.
Recent analysis of lock usage shows that the timer subsystem makes
heavy use of the lock. This patch introduces separate locks as to
avoid any contention between the qd_server_t and timer operations.
This closes #1350
> 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: Ken Giusti
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
