Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <15481235.post@talk.nabble.com>
Date: Thu, 14 Feb 2008 07:55:51 -0800 (PST)
From: ttmdev <joe.fernandez@ttmsolutions.com>
To: users@activemq.apache.org
Subject: Re: Maximum number of durable topics per MQ instance.
In-Reply-To: <74739121-E871-4F4F-A8BE-4B7910690A5F@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <15471104.post@talk.nabble.com>
 <74739121-E871-4F4F-A8BE-4B7910690A5F@gmail.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.