[ 
https://issues.apache.org/jira/browse/DISPATCH-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019497#comment-17019497
 ] 

ASF GitHub Bot commented on DISPATCH-1342:
------------------------------------------

franz1981 commented on issue #508: DISPATCH-1342 Replaced mutex with spin lock 
on qd_message content
URL: https://github.com/apache/qpid-dispatch/pull/508#issuecomment-576285823
 
 
   @astitcher @kgiusti That's the reason why I strongly suggest to replace 
mutexes on the router: 
https://twitter.com/forked_franz/status/1219241412497158144
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Replaced mutex with spin lock on qd_message content
> ---------------------------------------------------
>
>                 Key: DISPATCH-1342
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1342
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Routing Engine
>    Affects Versions: 1.7.0
>            Reporter: Francesco Nigro
>            Priority: Minor
>              Labels: performance
>
> Given that qd_message creation and qd_message_free involves sys_mutex 
> allocation/free and they are OS resources too, using spin locks will reduce 
> the CPU/memory usage while performing such frequent operations.
> In addition it would make the router more reactive and resilient to OS thread 
> scheduling while message->content is being concurrently accessed too, given 
> that such accesses are meant to not last long and there is no need to involve 
> OS arbitration to park/awake threads,



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to