You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2018/04/11 20:23:00 UTC
[jira] [Resolved] (PROTON-1672) Large deliveries comprising many
transfers are handled inefficiently
[ https://issues.apache.org/jira/browse/PROTON-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved PROTON-1672.
----------------------------------
Resolution: Fixed
> Large deliveries comprising many transfers are handled inefficiently
> --------------------------------------------------------------------
>
> Key: PROTON-1672
> URL: https://issues.apache.org/jira/browse/PROTON-1672
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: proton-j-0.23.0
> Reporter: Keith Wall
> Assignee: Timothy Bish
> Priority: Major
> Fix For: proton-j-0.27.0
>
> Attachments: JProfiler_PROTON-1672.tiff
>
>
> Running performance tests using Qpid Broker J and Qpid JMS Client (0.26.0) shows that receipt of large messages is very slow in comparison with the send of the same message. For instance, sending 300MiB bytes message takes 5 seconds on my laptop. The receipt takes 97 seconds.
> Instrumenting the client stack shows an obvious hot-spot in Proton-J. {{org.apache.qpid.proton.engine.impl.TransportSession#handleTransfer}} re-allocates/array copies the entire delivery buffer for ever transfer that comprises it. This leads to a non-linear loss of performance. The stack include Proton-J 0.23.0, but is looks like this code is unchanged.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org