[jira] [Updated] (NIFI-4902) ConsumeAMQP and PublishAMQP use a single connection, which results in poor performance
[ https://issues.apache.org/jira/browse/NIFI-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-4902: - Status: Patch Available (was: Open) > 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)
[jira] [Updated] (NIFI-4902) ConsumeAMQP and PublishAMQP use a single connection, which results in poor performance
[ https://issues.apache.org/jira/browse/NIFI-4902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Witt updated NIFI-4902: -- Resolution: Fixed Status: Resolved (was: Patch Available) +1 merged to master > 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)
