From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Network Performance between Win Host and Linux
Date: Wed, 12 Apr 2006 10:04:57 -0400 [thread overview]
Message-ID: <443D0909.3090806@win4lin.com> (raw)
In-Reply-To: <6fe044190604111536k944383o99ab27411d3864db@mail.gmail.com>
Hi Ken,
(all) the patches seem to work very well and be very stable with Windows
2000 guests here. I measured some SMB over TCP/IP transfers, and got
about a 1.5x downstream improvement and a 2x upstream improvement. You
will likely get more boost from less convoluted protocols like FTP or
something, but I didn't get around to testing that. Plus it's not clear
how much Windows itself is impeding the bandwidth. I am using
-kernel-kqemu.
2 additional things I noticed:
1. before your patches, the upstream transfers (guest->host) consumed
almost no CPU at all, but of course were much slower. Now, about half
the CPU gets used under heavy upstream load. The downstream, with
Windows guests at least, consumes 100% CPU the same as before. I
suspect you addressed this specifically with your select hack to avoid
the delay if there is pending slirp activity
2. overall latency "feels" improved as well, at least for basic stuff
like web browsing, etc. This is purely subjective.
Nice work! I'll be testing with a Linux VM soon and try to pin down
some better benchmarks, free of Windows clutter.
- Leo Reiter
Kenneth Duda wrote:
> The "qemu-slirp-performance" patch contains three improvements to qemu
> slirp networking performance. Booting my virtual machine (which
> NFS-mounts its root filesystem from the host) has been accelerated by
> 8x, from over 5 minutes to 40 seconds. TCP throughput has been
> accelerated from about 2 megabytes/sec to 9 megabytes/sec, in both
> directions (measured using a simple python script). The system is
> subjectively more responsive (for activities such as logging in or
> running simple python scripts).
>
> The specific problems fixed are:
>
> - the mss for the slirp-to-vm direction was 512 bytes (now 1460);
> - qemu would block in select() for up to four milliseconds at a
> time, even when data was waiting on slirp sockets;
> - slirp was deliberately delaying acks until timer expiration
> (TF_DELACK), preventing the vm from opening its send window, in
> violation of rfc2581.
>
> These fixes are together in one patch (qemu-slirp-performance.patch).
><snip>
--
Leonardo E. Reiter
Vice President of Product Development, CTO
Win4Lin, Inc.
Virtual Computing from Desktop to Data Center
Main: +1 512 339 7979
Fax: +1 512 532 6501
http://www.win4lin.com
next prev parent reply other threads:[~2006-04-12 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 17:20 [Qemu-devel] Network Performance between Win Host and Linux Kenneth Duda
2006-04-11 17:28 ` Paul Brook
2006-04-11 17:49 ` Kenneth Duda
2006-04-11 18:19 ` Helmut Auer
2006-04-12 2:10 ` Kazu
2006-04-11 20:40 ` Leonardo E. Reiter
2006-04-11 21:46 ` Kenneth Duda
2006-04-11 21:58 ` Leonardo E. Reiter
2006-04-11 22:42 ` Kenneth Duda
2006-04-11 21:00 ` Leonardo E. Reiter
2006-04-11 22:36 ` [Qemu-devel] " Kenneth Duda
2006-04-12 14:04 ` Leonardo E. Reiter [this message]
2006-04-12 18:19 ` Kenneth Duda
2006-04-12 18:26 ` Leonardo E. Reiter
2006-04-12 14:31 ` Leonardo E. Reiter
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=443D0909.3090806@win4lin.com \
--to=lreiter@win4lin.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 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).