You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by davewolfs <da...@gmail.com> on 2008/02/14 01:05:12 UTC
Maximum number of durable topics per MQ instance.
Hello everyone,
I am hoping that some of you could provide me with some realistic numbers on
the maximum number of Durable Topic subscribers.
I have never worked with Active MQ so I am not familiar with it's limits.
In a production environment what are some realistic numbers for the maximum
durable topic subscribers?
Is ActiveMQ capable of handling durable subscribers in the thousands i.e.
5000 subscribers or is a number like this pushing the limits.
Please advise.
Thank you,
Dave
--
View this message in context: http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15471104.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Maximum number of durable topics per MQ instance.
Posted by davewolfs <da...@gmail.com>.
You bring up some good points with respect to file descriptors. Any ideas
what the maximums are on an OS like linux? I was actually considering
modifying the REST Servlet so that it can support durable subscribers and if
this was the case then there is potential for a single JVM process to have
upwards of 3000 concurrent connections to the MQ server.
Do you see this as being a potential problem?
rajdavies wrote:
>
>
> On Feb 14, 2008, at 12:05 AM, davewolfs wrote:
>
>>
>> Hello everyone,
>>
>> I am hoping that some of you could provide me with some realistic
>> numbers on
>> the maximum number of Durable Topic subscribers.
>>
>> I have never worked with Active MQ so I am not familiar with it's
>> limits.
>> In a production environment what are some realistic numbers for the
>> maximum
>> durable topic subscribers?
>>
>> Is ActiveMQ capable of handling durable subscribers in the thousands
>> i.e.
>> 5000 subscribers or is a number like this pushing the limits.
>>
>> Please advise.
>>
>> Thank you,
>>
>> Dave
>> --
>> View this message in context:
>> http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15471104.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> ActiveMQ certainly is capable of handling a large number of durable
> subscribers - but I for one haven't tested the upper limit as yet.
> Factors which you need to take into account are:
>
> 1. A thread is associated with connection - unless you use AIO or NIO
> - so you need to ensure that your operating system allocate a large
> number of file descriptors per process. If messages cannot be pushed
> to the consumer straight away, they are pulled from data store - the
> thread from the sending connection - or the thread used to acknowledge
> messages from the consuming connection are used to do the polling.
>
> 2. Each durable subscriber adds a small overhead to the data store -
> its worthwhile trying different implementations - JDBC or the default
> file based store - to see which one is more suitable to your usage
> patterns
>
> Let us know how you get on!
>
>
>
> cheers,
>
> Rob
>
> http://open.iona.com/ -Enterprise Open Integration
> http://rajdavies.blogspot.com/
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15481210.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Maximum number of durable topics per MQ instance.
Posted by ttmdev <jo...@ttmsolutions.com>.
FYI - I downloaded AIO4J and give it a whirl against ActiveMQ 5. Unless I'm
missing something, AIO4J is not supported in ActiveMQ 5. The 'activeio' and
'aio' transport schemes (e.g., activeio:aio://localhost:61616 or
aio://localhost:61616) are not supported and there is no reference in the
activemq and activeio trunks to "com.ibm.io.*"
Joe
www.ttmsolutions.com
bsnyder wrote:
>
> On Thu, Feb 14, 2008 at 8:55 AM, ttmdev <jo...@ttmsolutions.com>
> wrote:
>>
>> Re the reference to "AIO", does this mean support for AIO4J or that
>> AMQ's use
>> of NIO is considered asynchronous i/o?
>
> It's a reference to AIO4J:
>
> http://www.alphaworks.ibm.com/tech/aio4j
>
> See the following for more information about using AIO with ActiveMQ:
>
> http://activemq.apache.org/how-do-i-configure-activemq-to-use-aio-server-transport.html
>
> I've not tried this with ActiveMQ 5 yet.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
>
> Blog: http://bruceblog.org/
>
>
--
View this message in context: http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15509070.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Maximum number of durable topics per MQ instance.
Posted by ttmdev <jo...@ttmsolutions.com>.
Thanks, Bruce.
Joe
bsnyder wrote:
>
> On Thu, Feb 14, 2008 at 8:55 AM, ttmdev <jo...@ttmsolutions.com>
> wrote:
>>
>> Re the reference to "AIO", does this mean support for AIO4J or that
>> AMQ's use
>> of NIO is considered asynchronous i/o?
>
> It's a reference to AIO4J:
>
> http://www.alphaworks.ibm.com/tech/aio4j
>
> See the following for more information about using AIO with ActiveMQ:
>
> http://activemq.apache.org/how-do-i-configure-activemq-to-use-aio-server-transport.html
>
> I've not tried this with ActiveMQ 5 yet.
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
>
> Blog: http://bruceblog.org/
>
>
--
View this message in context: http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15493463.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Maximum number of durable topics per MQ instance.
Posted by Bruce Snyder <br...@gmail.com>.
On Thu, Feb 14, 2008 at 8:55 AM, ttmdev <jo...@ttmsolutions.com> wrote:
>
> Re the reference to "AIO", does this mean support for AIO4J or that AMQ's use
> of NIO is considered asynchronous i/o?
It's a reference to AIO4J:
http://www.alphaworks.ibm.com/tech/aio4j
See the following for more information about using AIO with ActiveMQ:
http://activemq.apache.org/how-do-i-configure-activemq-to-use-aio-server-transport.html
I've not tried this with ActiveMQ 5 yet.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
Re: Maximum number of durable topics per MQ instance.
Posted by ttmdev <jo...@ttmsolutions.com>.
Re the reference to "AIO", does this mean support for AIO4J or that AMQ's use
of NIO is considered asynchronous i/o?
Joe
rajdavies wrote:
>
>
> On Feb 14, 2008, at 12:05 AM, davewolfs wrote:
>
>>
>> Hello everyone,
>>
>> I am hoping that some of you could provide me with some realistic
>> numbers on
>> the maximum number of Durable Topic subscribers.
>>
>> I have never worked with Active MQ so I am not familiar with it's
>> limits.
>> In a production environment what are some realistic numbers for the
>> maximum
>> durable topic subscribers?
>>
>> Is ActiveMQ capable of handling durable subscribers in the thousands
>> i.e.
>> 5000 subscribers or is a number like this pushing the limits.
>>
>> Please advise.
>>
>> Thank you,
>>
>> Dave
>> --
>> View this message in context:
>> http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15471104.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> ActiveMQ certainly is capable of handling a large number of durable
> subscribers - but I for one haven't tested the upper limit as yet.
> Factors which you need to take into account are:
>
> 1. A thread is associated with connection - unless you use AIO or NIO
> - so you need to ensure that your operating system allocate a large
> number of file descriptors per process. If messages cannot be pushed
> to the consumer straight away, they are pulled from data store - the
> thread from the sending connection - or the thread used to acknowledge
> messages from the consuming connection are used to do the polling.
>
> 2. Each durable subscriber adds a small overhead to the data store -
> its worthwhile trying different implementations - JDBC or the default
> file based store - to see which one is more suitable to your usage
> patterns
>
> Let us know how you get on!
>
>
>
> cheers,
>
> Rob
>
> http://open.iona.com/ -Enterprise Open Integration
> http://rajdavies.blogspot.com/
>
>
>
>
>
--
View this message in context: http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15481235.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Maximum number of durable topics per MQ instance.
Posted by Rob Davies <ra...@gmail.com>.
On Feb 14, 2008, at 12:05 AM, davewolfs wrote:
>
> Hello everyone,
>
> I am hoping that some of you could provide me with some realistic
> numbers on
> the maximum number of Durable Topic subscribers.
>
> I have never worked with Active MQ so I am not familiar with it's
> limits.
> In a production environment what are some realistic numbers for the
> maximum
> durable topic subscribers?
>
> Is ActiveMQ capable of handling durable subscribers in the thousands
> i.e.
> 5000 subscribers or is a number like this pushing the limits.
>
> Please advise.
>
> Thank you,
>
> Dave
> --
> View this message in context: http://www.nabble.com/Maximum-number-of-durable-topics-per-MQ-instance.-tp15471104s2354p15471104.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
ActiveMQ certainly is capable of handling a large number of durable
subscribers - but I for one haven't tested the upper limit as yet.
Factors which you need to take into account are:
1. A thread is associated with connection - unless you use AIO or NIO
- so you need to ensure that your operating system allocate a large
number of file descriptors per process. If messages cannot be pushed
to the consumer straight away, they are pulled from data store - the
thread from the sending connection - or the thread used to acknowledge
messages from the consuming connection are used to do the polling.
2. Each durable subscriber adds a small overhead to the data store -
its worthwhile trying different implementations - JDBC or the default
file based store - to see which one is more suitable to your usage
patterns
Let us know how you get on!
cheers,
Rob
http://open.iona.com/ -Enterprise Open Integration
http://rajdavies.blogspot.com/