lkml.org 
[lkml]   [2006]   [Nov]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: splice/vmsplice performance test results
On Mon, Nov 20 2006, Jens Axboe wrote:
> 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.

While I get that setup, can you repeat your testing without using
SPLICE_F_MORE (you don't really use that flag correctly, but it does not
matter for your case afaict) and SPLICE_F_MOVE? The latter will cost
some CPU, but vmsplice/splice for network receive to a file is not
really optimal in the first place. When we get splice() from socket fd
support that'll improve, right now you are doing the best you can.

--
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-11-20 09:29    [W:0.063 / U:5.968 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site