You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by "Suman.Patro-TRN" <Su...@lntebg.com> on 2015/10/28 05:21:53 UTC
regarding qpid C++ broker
Hello Sir,
I am currently evaluating qpid broker for its performance against other available brokers. So I would like to clear certain queries regarding the same.
Can anyone suggest the way to test the qpid broker against the following parameters:
1. Throughput
2. Latency
3.Memory Footprint
4.Persistence
5.Scalability
6.Failover mechanism
7.Communication patterns support
8.Security or cybersecurity involvement
9.Routing algorithm used and its complexity
I would like to find statistics on the same by practical evaluation , hence such a question.
Thanks and regards,
Suman
Larsen & Toubro Limited
www.larsentoubro.com
This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
Re: regarding qpid C++ broker
Posted by Virgilio Fornazin <vi...@gmail.com>.
We use it here in our business.
Is the AMQP of choice for throughtput & latency (we use 0.18-20 version,
planning to migrate to 0.34-5, we're testing to see if any regressions on
this side.
Memory footprint depends on how much messages will stay on queue if the
queue doesn't suport paging, you must test by yourself.
Persistent works good for us, scalability / failover worked so good with
0.18 series, in our 3-node cluster).
The communication patterns req-reply, pub-sub we use here, works like a
charm.
By the means 'routing', í'm assuming you're talking about the broker
exchanges (amq.topic). It's very efficient and fast.
On Wed, Oct 28, 2015 at 2:21 AM, Suman.Patro-TRN <Suman.Patro-TRN@lntebg.com
> wrote:
> Hello Sir,
> I am currently evaluating qpid broker for its
> performance against other available brokers. So I would like to clear
> certain queries regarding the same.
> Can anyone suggest the way to test the qpid broker against the
> following parameters:
> 1. Throughput
> 2. Latency
> 3.Memory Footprint
> 4.Persistence
> 5.Scalability
> 6.Failover mechanism
> 7.Communication patterns support
> 8.Security or cybersecurity involvement
> 9.Routing algorithm used and its complexity
> I would like to find statistics on the same by practical
> evaluation , hence such a question.
> Thanks and regards,
> Suman
>
> Larsen & Toubro Limited
>
> www.larsentoubro.com
>
> This Email may contain confidential or privileged information for the
> intended recipient (s). If you are not the intended recipient, please do
> not use or disseminate the information, notify the sender and delete it
> from your system.
>
Re: regarding qpid C++ broker
Posted by Gordon Sim <gs...@redhat.com>.
On 10/28/2015 02:01 PM, Chuck Rolke wrote:
> Quoting an old FAQ:
> ===
> There is a great resource supplied in the C++ broker test directory called perftest. If allows you to create load on a broker for all the exchanges, multiple queues, multiple connection, coordinate multiple publishing and consuming processes, benchmark transactions and much much more such as acquire mode, txn size, message size.
>
> For all the options
> {code}
> ./perftest --help
> {code}
> ===
Be aware though that qpid-perftest uses AMQP 0-10 only (and indeed the
now deprecated qpid::client API). There is also qpid-send and
qpid-receive, which along with the qpid-cpp-benchmark script provide a
similar tool that is more flexible.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: regarding qpid C++ broker
Posted by Chuck Rolke <cr...@redhat.com>.
Quoting an old FAQ:
===
There is a great resource supplied in the C++ broker test directory called perftest. If allows you to create load on a broker for all the exchanges, multiple queues, multiple connection, coordinate multiple publishing and consuming processes, benchmark transactions and much much more such as acquire mode, txn size, message size.
For all the options
{code}
./perftest --help
{code}
===
Perftest is executed many times during normal self test and examples of running it can be found there. If the order of your needs are the same as your priorities then you can start there and see that it gets you past some initial threshold.
Then refer to http://qpid.apache.org/releases/qpid-cpp-0.34/cpp-broker/book/index.html for more advanced topics.
----- Original Message -----
> From: "Suman.Patro-TRN" <Su...@lntebg.com>
> To: users@qpid.apache.org
> Sent: Wednesday, October 28, 2015 12:21:53 AM
> Subject: regarding qpid C++ broker
>
> Hello Sir,
> I am currently evaluating qpid broker for its performance
> against other available brokers. So I would like to clear
> certain queries regarding the same.
> Can anyone suggest the way to test the qpid broker against the following
> parameters:
> 1. Throughput
> 2. Latency
> 3.Memory Footprint
> 4.Persistence
> 5.Scalability
> 6.Failover mechanism
> 7.Communication patterns support
> 8.Security or cybersecurity involvement
> 9.Routing algorithm used and its complexity
> I would like to find statistics on the same by practical
> evaluation , hence such a question.
> Thanks and regards,
> Suman
>
> Larsen & Toubro Limited
>
> www.larsentoubro.com
>
> This Email may contain confidential or privileged information for the
> intended recipient (s). If you are not the intended recipient, please do not
> use or disseminate the information, notify the sender and delete it from
> your system.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org