Depends on disk, whether using Async etc... should easily be able to do
close to 100k/s before
you get into big disk configurations.
What client are you using? i.e. JMS is sync by default. quick testing
can be done with perftest and
using the durable options on perftest.
based on the numbers I expect you are running sync.. also are you using
txns?
Carl.
Shan Wang wrote:
I've just done a simple test, c++ client and server, message size is 500
bytes, deliveryProperity set to PERSISTENT, the queue is durable, using
default exchange, cluster and client are running in the same domain but
different hosts. The update rate achieved is about 100 message/second,
which is a bit lower than I expected. Have we done any comprehensive
tests about the update rate qpid can support? Is there any configuration
I can play with to increase the update rate?
Thanks,
Shan
The information contained in this email is strictly confidential and for the
use of the addressee only, unless otherwise indicated. If you are not the
intended recipient, please do not read, copy, use or disclose to others this
message or any attachment. Please also notify the sender by replying to this
email or by telephone (+44 (0)20 7896 0011) and then delete the email and any
copies of it. Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor endorsed by
it. IG Index plc is a company registered in England and Wales under number
01190902. VAT registration number 761 2978 07. Registered Office: Friars House,
157-168 Blackfriars Road, London SE1 8EZ. Authorised and regulated by the
Financial Services Authority. FSA Register number 114059.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
