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

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

ganeshmurthy commented on issue #514: DISPATCH-1349 qd_buffer_list_clone is 
wasting dst buffers available capacity
URL: https://github.com/apache/qpid-dispatch/pull/514#issuecomment-497795391
 
 
   My next observation is that the msg->ma_to_override, msg->ma_trace and 
msg->ma_ingress  always has at least one buffer associated with them even in 
the one router single sender, single receiver case.
   If we have only one router and the sender is not sending in any annotations 
and there is only one receiver on the same standalone router, why are these 
buffer populated in the first place and since they are populated, we are 
performing the extra overhead of copying them. If a message visits only one 
router in its lifetime, this seems like a waste of time 
 
----------------------------------------------------------------
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]


> qd_buffer_list_clone is wasting dst buffers available capacity
> --------------------------------------------------------------
>
>                 Key: DISPATCH-1349
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1349
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Routing Engine
>    Affects Versions: 1.7.0
>            Reporter: Francesco Nigro
>            Priority: Minor
>
> qd_buffer_list_clone is not filling completely destination buffers available 
> space (if any) after the first memcpy, allocating unnecessary qd_buffer(s)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to