Davies <[EMAIL PROTECTED]> wrote:
> You can try setting async dispatch on the consumer - see:
> http://activemq.apache.org/consumer-dispatch-async.html
> A separate task would be used then for dispatching to each consumer
>
> cheers.
>
> Rob
> On 21 Feb 2008, at 22:40
Yeah. Broker, consumer and producer are all in separate machine. All these
machines has 6-cpus.
The result for my throughput is total, not count for single consumer that is
why I feel strange of the results.
I also do some tests by using cluster of brokers, typically 3 broker
machines by using sto
I guess it is a warning for disconnect the clients which has been inactive
for a long time. You can set the time for inactive connection by set
activitymonitor.
On Thu, Feb 21, 2008 at 2:52 PM, sparky2708 <[EMAIL PROTECTED]> wrote:
>
> This started happening since we upgraded from 4.1.0. 4.1.0 d
; without write caching. That's slow, but it's also safe, and it's
> probably going to be fast enough for us.
>
> If anybody has any hints on how to make things go faster while still
> being safe, I'd love to hear them.
>
> Zao Liu wrote:
> > Yeah, I do ne
, the throughput is also get more than
3500/s for consuming
messages. I don't think to consuming messages which has been saved to store
will be so slow,
only 50 msgs/s.
Thanks,
Zao Liu
On Thu, Feb 21, 2008 at 11:52 AM, Ben Chobot <[EMAIL PROTECTED]> wrote:
> It sounds like you don
