You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Sivananda Reddys Thummala Abbigari <st...@salesforce.com> on 2015/05/15 09:15:14 UTC
Limitation on number of topics with in an exchange
Hi,
Broker: Java
Topic: amq.topic
Exchange, subscriber, messages are all durable. HA with BDB, with 1 replica.
My use case need large number of short lived topics. Each topics have 2
producers and 3 to 4 subscribers and a topic could live for an hour or so
at a maximum. Are there any limitations that could arise due to this for HA
perspective/in general(Can I have 50k concurrent topics with in a single
exchange?). Did any of you have done any tests related to this?. Please
let me know.
Thank you,
Siva.
Re: Limitation on number of topics with in an exchange
Posted by Rob Godfrey <ro...@gmail.com>.
On 15 May 2015 at 12:08, Sivananda Reddys Thummala Abbigari
<st...@salesforce.com> wrote:
> Hi Rob,
>
> are you using pattern matching (%, #) in your topic bindings or are they
> all exact match?
> No, they are exact match, as suggested I will try amq.direct
>
You don't need to use amq.direct, you could create a new direct
exchange "mytopics" or whatever you want to call it...
> Are you using durable subscriptions?
> Yes, I am using durable subscriptions
>
OK - do the durable subscriptions come and go every hour, or is it a
fairly fixed number of subscriptions just with the clients coming and
going every hour or so? Every time a subscription is created/deleted
then you are modifying the durable configuration which needs to be
replicated (and should be single threaded - though processing of
messages on other subscriptions on the same exchange is not affected).
I don't think that this will necessarily be a huge issue either way.
> Also, could you please confirm the following:
> When we sent a message using MessageProducer
> <http://docs.oracle.com/javaee/1.4/api/javax/jms/MessageProducer.html>.send(message),
> the default delivery mode is "PERSISTENT"?
>
That is indeed the default as per the JMS requirement.
Hoe this helps,
Rob
> Thank you,
> Siva.
>
> On Fri, May 15, 2015 at 12:39 AM, Rob Godfrey <ro...@gmail.com>
> wrote:
>
>> Hi Siva,
>>
>> are you using pattern matching (%, #) in your topic bindings or are
>> they all exact match? If you are using pattern matching and lots of
>> overlapping bindings then it's possible that the state machine that
>> gets built up for the matching engine can grow quite large in memory.
>> If you are not using pattern matching then you can actually just use a
>> direct exchange instead which will be more efficient. In terms of
>> performance I don't think there should be any issue with the pure
>> number of topics...
>>
>> Are you using durable subscriptions? If not I don't think the use of
>> HA really makes much difference as the subscriptions/messages won't be
>> replicated.
>>
>> -- Rob
>>
>> On 15 May 2015 at 09:15, Sivananda Reddys Thummala Abbigari
>> <st...@salesforce.com> wrote:
>> > Hi,
>> >
>> > Broker: Java
>> > Topic: amq.topic
>> > Exchange, subscriber, messages are all durable. HA with BDB, with 1
>> replica.
>> >
>> > My use case need large number of short lived topics. Each topics have 2
>> > producers and 3 to 4 subscribers and a topic could live for an hour or so
>> > at a maximum. Are there any limitations that could arise due to this for
>> HA
>> > perspective/in general(Can I have 50k concurrent topics with in a single
>> > exchange?). Did any of you have done any tests related to this?. Please
>> > let me know.
>> >
>> > Thank you,
>> > Siva.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Limitation on number of topics with in an exchange
Posted by Sivananda Reddys Thummala Abbigari <st...@salesforce.com>.
Hi Rob,
are you using pattern matching (%, #) in your topic bindings or are they
all exact match?
No, they are exact match, as suggested I will try amq.direct
Are you using durable subscriptions?
Yes, I am using durable subscriptions
Also, could you please confirm the following:
When we sent a message using MessageProducer
<http://docs.oracle.com/javaee/1.4/api/javax/jms/MessageProducer.html>.send(message),
the default delivery mode is "PERSISTENT"?
Thank you,
Siva.
On Fri, May 15, 2015 at 12:39 AM, Rob Godfrey <ro...@gmail.com>
wrote:
> Hi Siva,
>
> are you using pattern matching (%, #) in your topic bindings or are
> they all exact match? If you are using pattern matching and lots of
> overlapping bindings then it's possible that the state machine that
> gets built up for the matching engine can grow quite large in memory.
> If you are not using pattern matching then you can actually just use a
> direct exchange instead which will be more efficient. In terms of
> performance I don't think there should be any issue with the pure
> number of topics...
>
> Are you using durable subscriptions? If not I don't think the use of
> HA really makes much difference as the subscriptions/messages won't be
> replicated.
>
> -- Rob
>
> On 15 May 2015 at 09:15, Sivananda Reddys Thummala Abbigari
> <st...@salesforce.com> wrote:
> > Hi,
> >
> > Broker: Java
> > Topic: amq.topic
> > Exchange, subscriber, messages are all durable. HA with BDB, with 1
> replica.
> >
> > My use case need large number of short lived topics. Each topics have 2
> > producers and 3 to 4 subscribers and a topic could live for an hour or so
> > at a maximum. Are there any limitations that could arise due to this for
> HA
> > perspective/in general(Can I have 50k concurrent topics with in a single
> > exchange?). Did any of you have done any tests related to this?. Please
> > let me know.
> >
> > Thank you,
> > Siva.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Limitation on number of topics with in an exchange
Posted by Rob Godfrey <ro...@gmail.com>.
Hi Siva,
are you using pattern matching (%, #) in your topic bindings or are
they all exact match? If you are using pattern matching and lots of
overlapping bindings then it's possible that the state machine that
gets built up for the matching engine can grow quite large in memory.
If you are not using pattern matching then you can actually just use a
direct exchange instead which will be more efficient. In terms of
performance I don't think there should be any issue with the pure
number of topics...
Are you using durable subscriptions? If not I don't think the use of
HA really makes much difference as the subscriptions/messages won't be
replicated.
-- Rob
On 15 May 2015 at 09:15, Sivananda Reddys Thummala Abbigari
<st...@salesforce.com> wrote:
> Hi,
>
> Broker: Java
> Topic: amq.topic
> Exchange, subscriber, messages are all durable. HA with BDB, with 1 replica.
>
> My use case need large number of short lived topics. Each topics have 2
> producers and 3 to 4 subscribers and a topic could live for an hour or so
> at a maximum. Are there any limitations that could arise due to this for HA
> perspective/in general(Can I have 50k concurrent topics with in a single
> exchange?). Did any of you have done any tests related to this?. Please
> let me know.
>
> Thank you,
> Siva.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org