Shan Wang wrote:
I have increased the flush interval to as much as 10,000, but it didn't seem to help much. what I want to measure is the time for the application to hand off x messages to the library. If my application wants to push more than 5000 messages in one second, I need to make sure that qpid can take them and send them out quick enough without buffering a lot in memory.
I would try two things (1) try sending directly without the MessageReplayTracker and (2) try increasing the bounds on ConnectionSettings to increase the buffer space (I'm not sure what the default is for java).
I'd also suggest maybe using perftest (c++) or qpid-bench (java) to establish the sustainable throughput you can achieve for the desired size and durability. Any increase above this can only be temporary and will result in buffered data building up at one or more points in the chain (client library, senders network buffer, broker network buffer, broker queue).
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
