From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takuya Yoshikawa Subject: Re: Memory sync algorithm during migration Date: Tue, 15 Nov 2011 18:21:30 +0900 Message-ID: <4EC22F1A.2020601@oss.ntt.co.jp> References: <20111110163532.GE5656@spacemoose.devbln.europe.nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Oliver Hookins Return-path: Received: from serv2.oss.ntt.co.jp ([222.151.198.100]:48519 "EHLO serv2.oss.ntt.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753767Ab1KOJVA (ORCPT ); Tue, 15 Nov 2011 04:21:00 -0500 In-Reply-To: <20111110163532.GE5656@spacemoose.devbln.europe.nokia.com> Sender: kvm-owner@vger.kernel.org List-ID: Adding qemu-devel ML to CC. Your question should have been sent to qemu-devel ML because the logic is implemented in QEMU, not KVM. (2011/11/11 1:35), Oliver Hookins wrote: > Hi, > > I am performing some benchmarks on KVM migration on two different types of VM. > One has 4GB RAM and the other 32GB. More or less idle, the 4GB VM takes about 20 > seconds to migrate on our hardware while the 32GB VM takes about a minute. > > With a reasonable amount of memory activity going on (in the hundreds of MB per > second) the 32GB VM takes 3.5 minutes to migrate, but the 4GB VM never > completes. Intuitively this tells me there is some watermarking of dirty pages > going on that is not particularly efficient when the dirty pages ratio is high > compared to total memory, but I may be completely incorrect. You can change the ratio IIRC. Hopefully, someone who knows well about QEMU will tell you better ways. Takuya > > Could anybody fill me in on what might be going on here? We're using libvirt > 0.8.2 and kvm-83-224.el5.centos.1 > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html