qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Kirkland <jkirk...@redhat.com>
Subject Re: QPID performance on virtual machines
Date Wed, 02 May 2012 17:10:47 GMT
What sort of messging scenario is it?  Are the messages persisted?  How 
big are they?  If they are persisted are you using virtual disks or 
physical devices?

CLIVE wrote:
> Hi all,
>
> I have been undertaking some performance profiling of QPID version 
> 0.14 over the last few weeks and I have found a significant 
> performance drop off when running QPID in a virtual machine.
>
> As an example if I run qpidd on an 8 core DELL R710 with 36G RAM 
> (RHEL5u5) and then run qpid-perf-test (on the same machine to discount 
> any network problems) without any command line parameters I am seeing 
> about 85,000 publish transfers/sec and 80000 consume transfers/sec. If 
> I run the same scenario on a VM (tried both KVM and VMWare ESXi 4.3 
> running RHEL5u5) with 2 cores and 8G RAM, I am seeing only 45000 
> publish transfers/sec and 40000 consume transfers/sec. A significant 
> drop off in performance. Looking at the cpu and memory usage these 
> would not seem to be the limiting factors as the memory consumption of 
> qpidd stays under 200 MBytes and its CPU is up at about 150%; hence 
> the two core machine.
>
> I have even run the same test on my Mac Book at home using VMWare 
> Fusion 4 ( 2 Core 4G RAM) and see the same 45000/40000 transfers/sec 
> results.
>
> I would expect a small drop off in performance when running in a VM, 
> but not to the extent that I am seeing.
>
> Has anyone else seen this and if so were they able to get to the 
> bottom of the issue.
>
> Any help would be appreciated.
>
> Clive Lilley
>

-- 
James Kirkland
Principal Enterprise Solutions Architect
3340 Peachtree Road, NE,
Suite 1200
Atlanta, GA 30326 USA.
Phone (404) 254-6457 <https://www.google.com/voice#phones>
RHCE Certificate: 805009616436562

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message