All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Erik Jacobson <erikj@sgi.com>
Cc: Mark McLoughlin <markmc@redhat.com>, kvm@vger.kernel.org
Subject: Re: slow guest performance with build load, looking for ideas
Date: Thu, 09 Jul 2009 10:48:49 +0300	[thread overview]
Message-ID: <4A55A0E1.1060501@redhat.com> (raw)
In-Reply-To: <20090709023633.GB29409@sgi.com>

On 07/09/2009 05:36 AM, Erik Jacobson wrote:
>> Haven't followed the thread in great detail, but has anyone tried
>> putting the virtio disk back into rotational mode?
>>      
>
> Hello.  I haven't had a chance to try all the suggestions in the thread
> so far.  However, I did just run some tests with block queue rotation
> settings tonight.
>
> For the problem where mkfs.ext3 on a virtio disk image (raw image, not
> pre-allocated) the timing went from like 27 minutes for a 10gb fs down
> to just over 2 minutes.  So that was a huge difference.
>
> For the linux kernel build test, there was a difference, but less dramatic.
> I'd say the performance is still below what I expected.  I haven't given
> up yet, there is more to try in the thread.  I just wanted to post these
> results.
>
> The HW in use is the same as in the rest of the tread, including the
> virtio disk type.  Since my last post, fedora 11 updates have been
> applied to the system.
>
> Timing with the rotational stuff set to 1...
>
> real    14m13.015s
> user    29m42.162s
> sys     8m37.416s
>    

(user + sys) / real = 2.7

> And finally, to confirm the numbers on the host with no guest running...
> The same disk/filesystem, now mounted on the host instead of the guest, gave
> this timing:
>
> real    6m13.398s
> user    26m56.061s
> sys     5m34.477s
>    

(user + sys) / real = 5.2

I got 6.something in a guest!

> For the guest runs, qemu command was as follows.  For later tests, I will
> combine the queue rotation setting with the other suggestions.
>
> /usr/bin/qemu-kvm -M pc -m 4096 -smp 8 -name f11-test -uuid b7b4b7e4-9c07-22aa-0c95-d5c8a24176c5 -monitor pty -pidfile /var/run/libvirt/qemu//f11-test.pid -drive file=/var/lib/libvirt/images/f11-test.img,if=virtio,index=0,boot=on -drive file=/dev/sdb,if=virtio,index=1 -drive file=/var/lib/libvirt/images/test.img,if=virtio,index=2 -net nic,macaddr=54:52:00:46:48:0e,model=virtio -net user -serial pty -parallel none -usb -usbdevice tablet -vnc cct201:1 -soundhw es1370 -redir tcp:5555::22
>    

Please drop -usbdevice tablet and set the host I/O scheduler to 
deadline.  Add cache=none to the -drive options.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-07-09  7:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 21:04 slow guest performance with build load, looking for ideas Erik Jacobson
2009-06-14  9:33 ` Avi Kivity
2009-06-15 14:15   ` Erik Jacobson
2009-06-15 14:24     ` Avi Kivity
2009-06-15 15:25       ` Michael Tokarev
2009-06-15 15:27         ` Avi Kivity
2009-06-16  7:03           ` Michael Tokarev
2009-06-16  8:07             ` Avi Kivity
2009-06-18 23:07   ` Erik Jacobson
2009-06-28 14:17     ` Avi Kivity
2009-06-28 19:05       ` Erik Jacobson
2009-06-28 21:28         ` Avi Kivity
2009-07-01 21:41           ` Erik Jacobson
2009-07-02  5:48             ` Avi Kivity
2009-07-02  9:41               ` Avi Kivity
2009-07-03 15:43                 ` Mark McLoughlin
2009-07-03 16:28                   ` Erik Jacobson
2009-07-09  2:36                   ` Erik Jacobson
2009-07-09  7:48                     ` Avi Kivity [this message]
2009-07-09 18:01                       ` Erik Jacobson
2009-07-12  8:38                         ` Avi Kivity
2009-07-16 12:20                           ` Jes Sorensen
2009-07-25 14:33                             ` Avi Kivity
2009-07-03 10:41   ` Matty
2009-07-05  8:07     ` 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=4A55A0E1.1060501@redhat.com \
    --to=avi@redhat.com \
    --cc=erikj@sgi.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.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.