All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liuqiming (John)" <john.liuqiming@huawei.com>
To: xen-devel@lists.xensource.com
Cc: yang.z.zhang@Intel.com, peter.huangpeng@huawei.com
Subject: performace issue when turn on apicv
Date: Thu, 11 Jun 2015 15:23:58 +0800	[thread overview]
Message-ID: <5579378E.9020108@huawei.com> (raw)

Hi,

Recently I encounter a strange performance problem with APIC virtualization.

My host has Intel(R) Xeon(R) CPU E7-4890 v2 CPU installed which support 
APIC virtualization and x2apic, and there are 4 socket * 15 
cores_per_socket = 60 core available for VM. There is also a SSD disk on 
host and the host support vt-d, so I can passsthrough this SSD to VM.

A VM created with 60 vcpus,  400G memory and SSD device assigned.
I pin these vcpus 1:1 to phisical cpu, and in this VM only keep 15 vcpus
  online.

The problem is: when apicv turn on, a significant performace decrease 
can be observed and it seems related to cpu topology.

I had test follow cases
apicv=1:
1)  ONLINE VCPU {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14}
         PIN TO
            PCPU {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14}

2)  ONLINE VCPU {0,5,9,13,17,21,25,29,33,37,41,45,49,53,57}
         PIN TO
            PCPU {0,5,9,13,17,21,25,29,33,37,41,45,49,53,57}

apicv=0:
3)  ONLINE VCPU {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14}
         PIN TO
            PCPU {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14}

4)  ONLINE VCPU {0,5,9,13,17,21,25,29,33,37,41,45,49,53,57}
         PIN TO
            PCPU {0,5,9,13,17,21,25,29,33,37,41,45,49,53,57}

the result is (the lower the better):
1) 989
2) 2209
3) 978
4) 1130

It is a database testcase running on suse11sp3 system in the VM, and I 
had traced that "read" and "write" syscall get much slower in 2) case.

I have disabled NUMA in BIOS, so it seems apicv cause this bad 
performance when using cpus in different nodes.

Can any one shed some light on this?

Btw, I am using xen 4.1.5 version with apicv backported, so I am not 
sure whether something broken when backporting or just apicv behaves 
this way.

             reply	other threads:[~2015-06-11  7:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  7:23 Liuqiming (John) [this message]
2015-06-11  7:35 ` performace issue when turn on apicv Zhang, Yang Z
2015-06-11  8:09   ` Liuqiming (John)
2015-06-11  8:34     ` Zhang, Yang Z
2015-06-18  8:02       ` Liuqiming (John)
2015-06-18  8:20         ` Jan Beulich
2015-06-18  8:52           ` Jan Beulich
2015-06-18  8:53             ` Zhang, Yang Z
2015-06-18  9:15               ` Jan Beulich
2015-06-18  9:18                 ` Zhang, Yang Z
2015-06-18  9:35                   ` Jan Beulich
2015-06-19 14:23                     ` Konrad Rzeszutek Wilk
2015-06-18  9:31           ` Zhang, Yang Z
     [not found] <mailman.2928.1434616580.28840.xen-devel@lists.xen.org>
2015-06-18 14:55 ` Jiangyifei
2015-06-19 10:42   ` Jan Beulich
2015-06-22  2:48     ` Jiangyifei
2015-06-22  9:56       ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5579378E.9020108@huawei.com \
    --to=john.liuqiming@huawei.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yang.z.zhang@Intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.