Hi Matt & Brian,

It is my understanding that the Red Hat tests were conducted using a Real-time Version of RHEL (MRG) and that it was specifically tuned for MRG-M and its test applications.

You might want to try using the tuning application from the MRG install before you run the tests.

I hope this was helpful?

Best Regards .................... Ian

Ian Kinkade
CEO
Information Design, Inc.
145 Durham Road, Suite 11
Madison, CT  06443 USA
URL:   www.idi-middleware.com
Email: [email protected]

Work:  203-245-0772 Ext: 6212
Fax:   203-245-1885
Cell:  203-589-1192


On 7/26/2010 7:54 PM, Donohue, Matt wrote:
The last project I worked on was the same for me. Not close to the MRG 
throughput numbers with the same test and this was on an otherwise optimized 
trading box.
The MRG qpid rpm was faster than an Intel C++ compiled version though.

Regards,
Matt

-----Original Message-----
From: Brian Crowell [mailto:[email protected]]
Sent: Monday, July 26, 2010 3:18 PM
To: [email protected]
Subject: QPID message throughput - Red Hat numbers

Red Hat claims to be able to get hundreds of thousands of messages
through on an eight core machine
(http://www.redhat.com/mrg/messaging/features/ or
http://www.redhat.com/f/pdf/mrg/Reference_Architecture_MRG_Messaging_Throughput.pdf).
I'm working with an eight-core machine, and I'm only getting about
11,000/sec (in; about 6,500/sec out). This is with perftest, default
settings.

What kinds of things do I need to be doing to get better throughput?

--Brian

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to