You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andy LoPresto (JIRA)" <ji...@apache.org> on 2018/02/06 20:27:00 UTC
[jira] [Updated] (NIFI-4834) ConsumeJMS does not scale when given
more than 1 thread
[ https://issues.apache.org/jira/browse/NIFI-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy LoPresto updated NIFI-4834:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ConsumeJMS does not scale when given more than 1 thread
> -------------------------------------------------------
>
> Key: NIFI-4834
> URL: https://issues.apache.org/jira/browse/NIFI-4834
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.6.0
>
>
> When I run ConsumeJMS against a local broker, the performance is great. However, if I run against a broker that is running remotely with a 75 ms round trip time (i.e., somewhat high latency), then the performance is pretty poor, allowing me to receive only about 30-40 msgs/sec (1-2 MB/sec).
> Increasing the number of threads should result in multiple connections to the JMS Broker, which would provide better throughput. However, when I increase the number of Concurrent Tasks to 10, I see 10 consumers but only a single connection being created, so the throughput is no better (in fact it's a bit slower due to added lock contention).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)