From: Dor Laor <dlaor@redhat.com>
To: Javier Guerra <javier@guerrag.com>
Cc: Kenni Lund <kenni@kelu.dk>, Yan Vugenfirer <yvugenfi@redhat.com>,
kvm@vger.kernel.org, Vadim Rozenfeld <vrozenfe@redhat.com>
Subject: Re: Binary Windows guest drivers are released
Date: Fri, 25 Sep 2009 00:07:03 +0300 [thread overview]
Message-ID: <4ABBDF77.2060106@redhat.com> (raw)
In-Reply-To: <90eb1dc70909241359i41ba8d9rdcb8364289d740db@mail.gmail.com>
On 09/24/2009 11:59 PM, Javier Guerra wrote:
> On Thu, Sep 24, 2009 at 3:38 PM, Kenni Lund<kenni@kelu.dk> wrote:
>> I've done some benchmarking with the drivers on Windows XP SP3 32bit,
>> but it seems like using the VirtIO drivers are slower than the IDE drivers in
>> (almost) all cases. Perhaps I've missed something or does the driver still
>> need optimization?
>
> very interesting!
>
> it seems that IDE wins on all the performance numbers, but VirtIO
> always has lower CPU utilization. i guess this is guest CPU %, right?
> it would also be interesting to compare the CPU usage from the host
> point of view, since a lower 'off-guest' CPU usage is very important
> for scaling to many guests doing I/O.
>
Can you re-try it with setting the host ioscheduler to deadline?
Virtio backend (thread pool) is sensitive for it.
These drivers are mainly tweaked for win2k3 and win2k8. We once had
queue depth settings in the driver, not sure we still have it, Vadim,
can you add more info?
Also virtio should provide IO parallelism as opposed to IDE. I don't
think your test test it. Virtio can provide more virtual drives than the
max 4 that ide offers.
Dor
next prev parent reply other threads:[~2009-09-24 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 13:13 Binary Windows guest drivers are released Yan Vugenfirer
2009-09-24 19:23 ` Glennie Vignarajah
2009-09-24 20:38 ` Kenni Lund
2009-09-24 20:59 ` Javier Guerra
2009-09-24 21:07 ` Dor Laor [this message]
2009-09-25 6:52 ` Vadim Rozenfeld
2009-09-25 7:53 ` Kenni Lund
2009-09-25 9:01 ` Vadim Rozenfeld
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=4ABBDF77.2060106@redhat.com \
--to=dlaor@redhat.com \
--cc=javier@guerrag.com \
--cc=kenni@kelu.dk \
--cc=kvm@vger.kernel.org \
--cc=vrozenfe@redhat.com \
--cc=yvugenfi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).