of performing 4000
random IOP/s whatever the block size might be. I doubt that you ran your
experiments on a high-end disk array with hundreds of parallel spindles.
So, you need to understand your data flow first and adjust expectation
accordingly.
--
View this message in context:
http://www.nab
I am using Apache ActiveMQ 5.0. To my understand, dispatchSync only helpful
when have slower consumers and using the consumers using the same
connection, different sessions. But in my case, all consumer threads are
using different connections.
Thanks,
Zao
On Fri, Feb 22, 2008 at 1:28 AM, Rob Dav
Rob Davies wrote:
Writes are usually fast because of the journaling part of the default
message store
Which version are you using btw?
I'm using 5.0, and like I said in another email, when writing safely
(syncOnWrite="true") performance isn't all that good without write
caching. How do you d
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, Zao Liu wrote:
Another issue I met is when I increase the number of consum
On 21 Feb 2008, at 19:52, Ben Chobot wrote:
It sounds like you don't have a very firm grasp on what's going on,
under the covers. If you need persistence, have you tried pulling
the power cord from your server and verifying you haven't lost
messages? If you don't care, why do you need pers
Another issue I met is when I increase the number of consumers for testing
non-persistent messages,
the throughput also get down very fast. I can't find the reason for it.
Each consumer thread is a separate connection to the broker.
Below is my result for testing (all using one producer to send mes
Well, I'm just starting to play with ActiveMQ myself, but just as a
datapoint, I found that when writing every durable message to disk using
the default Kaha store in 5.0, I maxed out at transferring a whopping 14
40KB msgs/s. That's using a single, low-performance 7200RPM drive
without write c
Yeah, I do need to test for persistence, but firstly I wan to make sure the
performance
is good. The result for consuming durable messages make me disappointed. Is
any specific
configuration for consuming durable messages? I do test for producing and
consuming
durable messages at the same time, th
It sounds like you don't have a very firm grasp on what's going on,
under the covers. If you need persistence, have you tried pulling the
power cord from your server and verifying you haven't lost messages? If
you don't care, why do you need persistence? :)
I suspect that what might be happeni
messages is 50 msgs/s and I
>> found the rate is keeping going down with time.
>>
>> Any comments or suggestions?
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Performance-issue-for-ActiveMQ-Server-tp15617616s2354p15618683.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
What is the underlying I/O system like for your broker? As I understand
the persistence layer for ActiveMQ, 3,500 durable messages a second
sounds too good to be true, assuming you're writing them safely.
zaoliu wrote:
I am tuning the performance of ActiveMQ broker for Queue by using three
sep
consume messages. The ave time for consume messages is 50 msgs/s and I
found the rate is keeping going down with time.
Any comments or suggestions?
--
View this message in context:
http://www.nabble.com/Performance-issue-for-ActiveMQ-Server-tp15617616s2354p15617616.html
Sent from the ActiveMQ - User
12 matches
Mail list logo
