From: Willy Tarreau <w@1wt.eu>
To: "Patrick J. LoPresti" <lopresti@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Is splice() useful without page stealing?
Date: Fri, 18 Dec 2009 07:34:54 +0100 [thread overview]
Message-ID: <20091218063454.GD32739@1wt.eu> (raw)
In-Reply-To: <23986fd90912171847w6d46ba2bx9d8763a63fc758c3@mail.gmail.com>
On Thu, Dec 17, 2009 at 06:47:19PM -0800, Patrick J. LoPresti wrote:
(...)
> Now, if splice() actually let you do things like flip pages from the
> network stack into the page cache with zero copies, then I could see
> the point. As it is, I am curious to know:
>
> 1) Does anybody have any actual benchmarks showing performance
> advantages for splice() over read()/write()? If so, can I obtain the
> benchmark code?
I did this for TCP->TCP sockets, and the gain is huge at high
bit rates (10 Gbps). Basically, 10 Gbps at 20% CPU with splice,
100% CPU with recv/send. You can find the test results here :
http://haproxy.1wt.eu/10g.html
I'm not using splice for disk-to-net nor net-to-disk transfers though.
Willy
prev parent reply other threads:[~2009-12-18 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 2:47 Is splice() useful without page stealing? Patrick J. LoPresti
2009-12-18 6:34 ` Willy Tarreau [this message]
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=20091218063454.GD32739@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=lopresti@gmail.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