[
https://issues.apache.org/jira/browse/NIFI-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404989#comment-16404989
]
ASF subversion and git services commented on NIFI-4902:
-------------------------------------------------------
Commit 39556e35131638bfb5795dd41736c0faae8aaf39 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=39556e3 ]
NIFI-4902: This closes #2485. Updated ConsumeAMQP, PublishAMQP to use one
connection per concurrent task instead of a single connection shared by all
concurrent tasks. This offers far better throughput when the network latency is
non-trivial. Also refactored to simplify code
Signed-off-by: joewitt <[email protected]>
> ConsumeAMQP and PublishAMQP use a single connection, which results in poor
> performance
> --------------------------------------------------------------------------------------
>
> Key: NIFI-4902
> URL: https://issues.apache.org/jira/browse/NIFI-4902
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.6.0
>
>
> PublishAMQP and ConsumeAMQP both use a single underlying connection,
> regardless of how many concurrent tasks are available. As a result, this
> leads to poor performance when the network latency is not extremely small.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)