From: Michael Tokarev <mjt@tls.msk.ru>
To: Bug 524447 <524447@bugs.launchpad.net>
Cc: Dave Walker <davewalker@ubuntu.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 524447] Re: virsh save is very slow
Date: Mon, 14 Jun 2010 14:57:39 +0400 [thread overview]
Message-ID: <4C160B23.6000809@msgid.tls.msk.ru> (raw)
In-Reply-To: <20100614093732.19949.71109.malone@palladium.canonical.com>
14.06.2010 13:37, Dave Walker wrote:
> Changing to libvirt as commentary here, and on the upstream bug report
> by Cole indicate a fix has been commit that improves this performance.
Um. This is not that simple, apparently.
I did some tests after this bug were discussed/mentioned last time,
and see absolutely no difference between 512 and 1M dd block size.
Well, there IS some difference, like several percents, but it is
still very slow, and is doing nothing -- the machine is 99% idle
while saving the state. Also, when using, say, gzip or lzop in
place of dd (both of them perform input in units larger than 512
bytes), it is still as slow.
strace shows one of kvm threads is slowly poking eventfd all the
time, while others are doing right to nothing.
It looks like some bad timing issue. The fact that changing block
size helps sometimes - I think it's because the improvements of
timing (mix-n-match), not because of real improvements.
> ** Package changed: qemu-kvm (Ubuntu) => libvirt (Ubuntu)
In any way, the problem is definitely NOT in libvirt, since the
same slowness is observed without libvirt.
Thanks!
/mjt
next prev parent reply other threads:[~2010-06-14 10:57 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100219141749.18571.12250.malonedeb@wampee.canonical.com>
2010-06-02 15:05 ` [Qemu-devel] [Bug 524447] Re: virsh save is very slow Anthony Liguori
2010-06-02 16:16 ` Anthony Liguori
2010-06-02 16:39 ` Cole Robinson
2010-06-14 9:37 ` Dave Walker
2010-06-14 10:57 ` Michael Tokarev [this message]
2010-06-14 11:18 ` Dave Walker
2010-06-15 10:07 ` Chris Bainbridge
2010-06-15 13:30 ` Laine Stump
2010-06-22 19:02 ` Serge Hallyn
2010-07-07 17:40 ` Nikola Ciprich
2010-07-07 18:11 ` Iggy
2010-08-03 7:52 ` Frederic Van Espen
2010-11-28 1:48 ` earl
2010-11-29 14:59 ` Serge Hallyn
2010-11-29 14:59 ` Serge Hallyn
2010-12-27 11:35 ` EsbenHaabendal
2011-01-03 12:46 ` Paolo Bonzini
2011-01-03 13:23 ` EsbenHaabendal
2011-01-03 13:56 ` Michael Tokarev
2011-01-03 14:23 ` EsbenHaabendal
2011-01-07 16:01 ` Serge Hallyn
2011-03-14 22:27 ` Serge Hallyn
2011-03-15 0:58 ` Serge Hallyn
2011-03-15 1:28 ` Serge Hallyn
2011-03-15 1:44 ` Serge Hallyn
2011-03-24 12:38 ` dum8d0g
2011-03-24 14:55 ` Serge Hallyn
2011-03-24 14:56 ` Serge Hallyn
2011-03-24 17:00 ` dum8d0g
2011-03-24 17:01 ` dum8d0g
2011-03-24 21:06 ` Serge Hallyn
2011-07-22 2:16 ` Jeff Snider
2011-07-22 3:10 ` Serge Hallyn
2011-07-22 3:11 ` Serge Hallyn
2011-07-22 3:20 ` Serge Hallyn
2011-07-22 3:25 ` Jeff Snider
2011-07-22 3:25 ` Serge Hallyn
2011-07-22 18:01 ` Clint Byrum
2011-07-23 0:36 ` Jeff Snider
2011-07-23 6:33 ` Clint Byrum
2011-07-27 15:50 ` Jamie Strandboge
2011-07-27 16:14 ` Serge Hallyn
2011-07-27 18:11 ` Jeff Snider
2011-07-28 5:02 ` Chris Halse Rogers
2011-07-28 6:49 ` Michael Tokarev
2011-07-28 14:05 ` Jeff Snider
2011-07-28 14:21 ` Michael Tokarev
2011-08-11 1:22 ` Bug Watch Updater
2012-01-28 19:10 ` BenLake
2012-01-30 23:08 ` Serge Hallyn
2012-02-17 9:43 ` Martin Pitt
2012-02-20 4:42 ` Jeff Snider
2012-02-20 15:54 ` Clint Byrum
2012-03-02 16:43 ` BenLake
2012-03-02 18:01 ` Clint Byrum
2012-03-02 18:41 ` Jeff Snider
2012-03-10 5:27 ` Jeff Snider
2012-03-14 19:48 ` Launchpad Bug Tracker
2012-03-29 3:25 ` BenLake
2017-10-28 0:22 ` Bug Watch Updater
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=4C160B23.6000809@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=524447@bugs.launchpad.net \
--cc=davewalker@ubuntu.com \
--cc=qemu-devel@nongnu.org \
/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.