Re: Perf regression of netperf compared Xen 4.4 to origin/master

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Thu, Jul 03, 2014 at 11:46:30AM +0100, George Dunlap wrote:
> On Wed, Jul 2, 2014 at 5:55 PM, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> > On 02/07/14 17:52, Konrad Rzeszutek Wilk wrote:
> >> The test is pretty silly.
> >>
> >> I've 14 guests, and I make each guest run netperf against the other.
> >> I start with 1 pair, then 2 pairs, then up to 7. Each guest
> >> is 768 MB, runs in a RAMdisk and just has one vif. The box is
> >> a SuperMicro X8DB8+ with two E5520 and 12GB of RAM.
> >> The netperf runs for a minute. The guests are PVHVM and I am
> >> using qemu-upstream.  The guest configs are:
> >>
> >> builder='hvm'
> >> disk = [ 'file:/mnt/lab/bootstrap-x86_64/root_image.iso,hdc:cdrom,r']
> >> memory=768
> >> boot='d'
> >> vcpus=1
> >> serial='file:/var/log/xen/console-g-vm0.log'
> >> vnclisten='0.0.0.0'
> >> name='g-vm0'
> >> on_crash='preserve'
> >> # IP is 192.168.102.90
> >> vif = [ 'mac=00:0f:4b:01:01:00, bridge=switch' ]
> >> .. and naturally the ip, name and MAC change for each guest.
> >>
> >> The kernel for both the guest and domain 0 is the same - no
> >> configuration change. The Xen is built without debug=y.
> >
> > What do you mean by this?  master has debugging enabled by default so
> > unless you build with debug=n, you will have a debug build.
> 
> You don't know how many times I've tripped over this...

<end flushes>

Whew. It was indeed that, and next time I have to make that part of
my checklist before sending to xen-devel!

> 
>  -George