On Wed, Dec 15, 2010 at 10:56 AM, Stanislaw Kogut <sko...@sistyma.net> wrote:
> On Wed, Dec 15, 2010 at 7:37 PM, Bruce Snyder <bruce.sny...@gmail.com>wrote:
>
>> On Wed, Dec 15, 2010 at 10:32 AM, Stanislaw Kogut <sko...@sistyma.net>
>> wrote:
>> > I already tried every topic here, with no significant effect.
>> > I'm already using KahaDB for peristence (even placing it's data to
>> tmpfs).
>> > I can't use async send/receive, as I need reliable transport.
>> > I'm using transactions (this is a requirement).
>>
>> How about your KahaDB settings? Try this:
>>
>> <kahaDB directory="${activemq.base}/data/kahadb"
>> enableJournalDiskSyncs="false"
>> indexWriteBatchSize="10000"
>> indexCacheSize="1000"/>
>>
>> Already have this in config file.
>
>
>> > What about multiple consumers? Should they use one or many different
>> > connection factories or sessions to consume faster?
>>
>> Creating multiple sessions from a single connection works well.
>>
>> Ok then.
> What about further scalability of queue? It is very probably I will need to
> send more and more messages. Will distributing queue over many brokers help
> with throughput without significant latency impact? Or there is only way to
> scale up with hardware for broker?
Please provide your broker config file so we can have a look.
Another item, have you disabled the dedicated task runner in the
ActiveMQ start script?
Also, have you read through this article?:
http://fusesource.com/wiki/display/ProdInfo/Understanding+the+Threads+Allocated+in+ActiveMQ
Bruce
--
perl -e 'print
unpack("u30","D0G)u8...@4vyy9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
