[
https://issues.apache.org/jira/browse/QPID-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823788#comment-13823788
]
Flavio Baronti commented on QPID-5334:
--------------------------------------
With this code, how can I know for which binding the message was sent to the
receiver? In the example the bindings are simple, but in the actual application
I will have bindings with * and #, so a simple string compare with qpid.subject
is not sufficient.
> Low throughput with thousands of queues
> ---------------------------------------
>
> Key: QPID-5334
> URL: https://issues.apache.org/jira/browse/QPID-5334
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, Java Client
> Affects Versions: 0.24
> Environment: Broker: Linux 2.6.32 64bit
> Client: Windows 7, Java 1.7.0_21 64bit
> Reporter: Flavio Baronti
> Labels: performance
> Attachments: JMSGenerator.java, JMSReceiver.java,
> use_shared_session_queue.patch
>
>
> I have an use case where I need to create hundreds of thousands of queues,
> each one subscribed to a different topic (therefore I have as many topics
> as queues).
> I set up a test with a single producer generating data on a randomly
> chosen topic, and a receiver retrieving data from the queues (and throwing
> it away).
> I'm using the JMS api, and doing the obvious thing makes the throughput
> drop dramatically from 10k msg/sec with a single topic/queue (around the
> top my network adapter can sustain) to 20 msg/sec with 100k topics/queues.
> I found out that I can recover performance by using more JMS sessions and
> connections - e.g. create 4 connections with 100 sessions each, and
> randomly distributing the receiving queues on them.
> This however is less than ideal, since with the JMS client a thread is
> created for each session, I can manage the workload with 1 thread only when
> it's over a single queue.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
