You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by dmounessa <dm...@yahoo.com> on 2011/12/06 19:01:59 UTC

C++ Broker Performance for Durable Queues vs Topic

1. Is there any performance matrix of durable queues with message size and os
version?
 
   I would like to compare my test results against what is in actual
production? 

    How many message per seconds should I expect for one broker for 1024
bytes message sent to a durable queue?

    Will clustering reduces the broker's throughput and if yes by how much?

2. It seems that No-Persistent Queue without Store Module and Topic should
have same throughput. However, I see the queues that are not
durable/non-persistence messages have worse message rate per second than
sending the messages to the topic -- 
Is this correct does any one can explain this?
  

3. Does JMS client or C++ Client improve the Broker's overall message
processing or is it indifferent?
 

Thanks for any information on this.


--
View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/C-Broker-Performance-for-Durable-Queues-vs-Topic-tp7067759p7067759.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: C++ Broker Performance for Durable Queues vs Topic

Posted by Carl Trieloff <cc...@redhat.com>.

no, just drop the tcp option from your connection address if in use.  If
not, then I'll let Kim pick up and comment on the thread.

Carl.


On 12/06/2011 02:25 PM, dmounessa wrote:
> I am using geronimo-jms_1.1_spec-1.0.jar 
>
> Do I need a new version? was this released?
>
>
>
> --
> View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/C-Broker-Performance-for-Durable-Queues-vs-Topic-tp7067759p7068061.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: C++ Broker Performance for Durable Queues vs Topic

Posted by dmounessa <dm...@yahoo.com>.
I am using geronimo-jms_1.1_spec-1.0.jar 

Do I need a new version? was this released?



--
View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/C-Broker-Performance-for-Durable-Queues-vs-Topic-tp7067759p7068061.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: C++ Broker Performance for Durable Queues vs Topic

Posted by Carl Trieloff <cc...@redhat.com>.
On 12/06/2011 01:01 PM, dmounessa wrote:
> 2. It seems that No-Persistent Queue without Store Module and Topic should
> have same throughput. However, I see the queues that are not
> durable/non-persistence messages have worse message rate per second than
> sending the messages to the topic -- 
> Is this correct does any one can explain this?

which client?  Kim recently uncovered a bug in JMS client setting
tcp_nodelay with exhibits this behavior.

>   
>
> 3. Does JMS client or C++ Client improve the Broker's overall message
> processing or is it indifferent?


C++ is faster.

Carl.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Re: C++ Broker Performance for Durable Queues vs Topic

Posted by Fraser Adams <fr...@blueyonder.co.uk>.
dmounessa wrote:
> 1. Is there any performance matrix of durable queues with message size and os
> version?
>  
>    I would like to compare my test results against what is in actual
> production? 
>
>     How many message per seconds should I expect for one broker for 1024
> bytes message sent to a durable queue?
>
>     Will clustering reduces the broker's throughput and if yes by how much?
>   
I'm not aware of any such matrix - and clearly if such a thing existed 
it would be "relative" I guess that it's stating the obvious that it 
would depend hugely on your set up.

One thing worth playing with is qpid-perftest which lives in the 
cpp/tests directory. Note that this is really a broker load test so it 
doesn't represent what a *real* client might do (for example it 
generally creates one message outside the critical path and continually 
sends that in the loop), but it'll allow you to get a really good 
picture of what you need to do with your broker/network/client topology 
to get maximum performance.
> 2. It seems that No-Persistent Queue without Store Module and Topic should
> have same throughput. However, I see the queues that are not
> durable/non-persistence messages have worse message rate per second than
> sending the messages to the topic -- 
> Is this correct does any one can explain this?
>   
>
> 3. Does JMS client or C++ Client improve the Broker's overall message
> processing or is it indifferent?
>  
>
> Thanks for any information on this.
>   
Go on, have a guess :-)

The Java JMS client is definitely quite a lot slower, though to be fair 
it still rocks compared to any other JMS provider I've come across. In 
my more obtuse moments I keep getting tempted to write a JMS wrapper 
around a SWIG binding to the c++ qpid::messaging API to do a back to 
back comparison :-D

>
> --
> View this message in context: http://apache-qpid-users.2158936.n2.nabble.com/C-Broker-Performance-for-Durable-Queues-vs-Topic-tp7067759p7067759.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
>
>
>   


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org