From: Avi Kivity <avi@redhat.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
"Yang, Xiaowei" <xiaowei.yang@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
"Li, Xin" <xin.li@intel.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: VM performance issue in KVM guests.
Date: Tue, 13 Apr 2010 09:46:16 +0300 [thread overview]
Message-ID: <4BC41338.80206@redhat.com> (raw)
In-Reply-To: <EB8593BCECAB3D40A8248BE0B6400A38469046C1@shzsmsx502.ccr.corp.intel.com>
On 04/13/2010 03:50 AM, Zhang, Xiantao wrote:
> Avi Kivity wrote:
>
>> On 04/12/2010 05:04 AM, Zhang, Xiantao wrote:
>>
>>>
>>>> What was the performance hit? What was your I/O setup (image
>>>> format, using aio?)
>>>>
>>>>
>>> The issue only happens when vcpu number is over-committed(e.g.
>>> vcpu/pcpu>2) and physical cpus are saturated. For example, when run
>>> webbench in windows OS in this case, its performance drops by 80%.
>>> In our experiment, we are using image file through virtio, and I
>>> think aio should be used by default also.
>>>
>>>
>> Is this on a machine that does pause-loop exits? The current handing
>> of PLE is very suboptimal. With proper directed yield we should be
>> much better there.
>>
>> Without PLE, we need paravirtualized spinlocks, no way around it.
>>
> PLE has the ability to eliminate the issue at some extent, and pv solution should be helpful also. But for windows guests running on machines without PLE, we still needs to enhance host side to resolve the issue.
>
Well, was this on a machine with PLE or without PLE?
>> Spin loops need to be addressed first, they are known to kill
>> performance in overcommit situations.
>>
> Even in overcommit case, if vcpu threads of one qemu are not scheduled or pulled to the same logical processor, the performance drop is tolerant like Xen's case today. But for KVM, it has to suffer from additional performance loss, since host's scheduler actively pulls these vcpu threads together.
>
>
Can you quantify this loss? Give examples of what happens?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-04-13 6:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EB8593BCECAB3D40A8248BE0B6400A3846903F4C@shzsmsx502.ccr.corp.intel.com>
2010-04-10 19:27 ` VM performance issue in KVM guests Avi Kivity
2010-04-12 2:04 ` Zhang, Xiantao
2010-04-12 6:40 ` Avi Kivity
2010-04-13 0:50 ` Zhang, Xiantao
2010-04-13 6:46 ` Avi Kivity [this message]
2010-04-14 3:24 ` Zhang, Xiantao
2010-04-14 8:14 ` Avi Kivity
2010-04-16 2:27 ` Zhang, Xiantao
2010-04-17 19:02 ` Avi Kivity
[not found] ` <p2o2eae271004142158xaa5da968ueff0c2afe6894f9d@mail.gmail.com>
2010-04-15 8:18 ` Avi Kivity
2010-04-15 13:33 ` Peter Zijlstra
2010-04-15 16:43 ` Srivatsa Vaddagiri
2010-04-16 10:40 ` Peter Zijlstra
2010-04-19 1:32 ` Zhang, Xiantao
2010-04-17 19:04 ` Avi Kivity
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=4BC41338.80206@redhat.com \
--to=avi@redhat.com \
--cc=eddie.dong@intel.com \
--cc=efault@gmx.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=peterz@infradead.org \
--cc=xiantao.zhang@intel.com \
--cc=xiaowei.yang@intel.com \
--cc=xin.li@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox