From: Jens Axboe <jens.axboe@oracle.com>
To: Jim Schutt <jaschut@sandia.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: splice/vmsplice performance test results
Date: Mon, 20 Nov 2006 08:59:42 +0100 [thread overview]
Message-ID: <20061120075941.GF4077@kernel.dk> (raw)
In-Reply-To: <1163784110.8170.8.camel@sale659.sandia.gov>
On Fri, Nov 17 2006, Jim Schutt wrote:
> On Thu, 2006-11-16 at 21:25 +0100, Jens Axboe wrote:
> > On Thu, Nov 16 2006, Jim Schutt wrote:
> > > Hi,
> > >
>
> > > My test program can do one of the following:
> > >
> > > send data:
> > > A) read() from file into buffer, write() buffer into socket
> > > B) mmap() section of file, write() that into socket, munmap()
> > > C) splice() from file to pipe, splice() from pipe to socket
> > >
> > > receive data:
> > > 1) read() from socket into buffer, write() buffer into file
> > > 2) ftruncate() to extend file, mmap() new extent, read()
> > > from socket into new extent, munmap()
> > > 3) read() from socket into buffer, vmsplice() buffer to
> > > pipe, splice() pipe to file (using the double-buffer trick)
> > >
> > > Here's the results, using:
> > > - 64 KiB buffer, mmap extent, or splice
> > > - 1 MiB TCP window
> > > - 16 GiB data sent across network
> > >
> > > A) from /dev/zero -> 1) to /dev/null : 857 MB/s (6.86 Gb/s)
> > >
> > > A) from file -> 1) to /dev/null : 472 MB/s (3.77 Gb/s)
> > > B) from file -> 1) to /dev/null : 366 MB/s (2.93 Gb/s)
> > > C) from file -> 1) to /dev/null : 854 MB/s (6.83 Gb/s)
> > >
> > > A) from /dev/zero -> 1) to file : 375 MB/s (3.00 Gb/s)
> > > A) from /dev/zero -> 2) to file : 150 MB/s (1.20 Gb/s)
> > > A) from /dev/zero -> 3) to file : 286 MB/s (2.29 Gb/s)
> > >
> > > I had (naively) hoped the read/vmsplice/splice combination would
> > > run at the same speed I can write a file, i.e. at about 450 MB/s
> > > on my setup. Do any of my numbers seem bogus, so I should look
> > > harder at my test program?
> >
> > Could be read-ahead playing in here, I'd have to take a closer look at
> > the generated io patterns to say more about that. Any chance you can
> > capture iostat or blktrace info for such a run to compare that goes to
> > the disk?
>
> I've attached a file with iostat and vmstat results for the case
> where I read from a socket and write a file, vs. the case where I
> read from a socket and use vmsplice/splice to write the file.
> (Sorry it's not inline - my mailer locks up when I try to
> include the file.)
>
> Would you still like blktrace info for these two cases?
No, I think the iostat data is fine, I don't think the blktrace info
would give me any more insight on this problem. I'll set up a test to
reproduce it here, looks like the write out path could be optimized some
more.
--
Jens Axboe
next prev parent reply other threads:[~2006-11-20 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 18:08 splice/vmsplice performance test results Jim Schutt
2006-11-16 20:25 ` Jens Axboe
2006-11-16 21:24 ` Jim Schutt
2006-11-17 17:21 ` Jim Schutt
2006-11-20 7:59 ` Jens Axboe [this message]
2006-11-20 8:24 ` Jens Axboe
2006-11-20 15:49 ` Jim Schutt
2006-11-21 13:54 ` Jens Axboe
2006-11-21 19:17 ` Jim Schutt
2006-11-22 8:57 ` Jens Axboe
2006-11-22 22:35 ` Jim Schutt
2006-11-23 11:24 ` Jens Axboe
2006-11-27 20:57 ` Jim Schutt
2006-11-16 20:52 ` David Miller
2006-11-16 21:21 ` Jens Axboe
2006-11-16 21:27 ` David Miller
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=20061120075941.GF4077@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=jaschut@sandia.gov \
--cc=linux-kernel@vger.kernel.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