You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/11/04 02:49:58 UTC
[jira] [Updated] (PROTON-659) if protons internal buffer gets
large, performance can suffer
[ https://issues.apache.org/jira/browse/PROTON-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross updated PROTON-659:
-------------------------------
Fix Version/s: 0.17.0
> if protons internal buffer gets large, performance can suffer
> -------------------------------------------------------------
>
> Key: PROTON-659
> URL: https://issues.apache.org/jira/browse/PROTON-659
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Affects Versions: 0.7
> Reporter: Gordon Sim
> Priority: Minor
> Labels: perf
> Fix For: 0.17.0
>
>
> In doing some performance investigations using qpid::messaging over 1.0, in particular as message size got larger, I saw much lower throughput and lots of cpu used. From callgrind it looked like this was from shuffliing up the buffer in pn_dispatcher_output. Because of the threading in qpid::messaging, it was possible for the application to generate too much output using the top-half of the engine API before the IO was done for the bottom half. Fixing that in qpid:messaging improved performance.
> There may perhaps be something that proton could do to make users more aware of this (e.g. a log message if the buffer exceeds a certain size? or just documentation?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org