From: Jim Nance <jlnance@sdf.lonestar.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: sendfile() with 100 simultaneous 100MB files
Date: Sun, 22 Jan 2006 14:24:01 +0000 [thread overview]
Message-ID: <20060122142401.GA24738@SDF.LONESTAR.ORG> (raw)
In-Reply-To: <9e4733910601201353g36284133xf68c4f6eae1344b4@mail.gmail.com>
On Fri, Jan 20, 2006 at 04:53:44PM -0500, Jon Smirl wrote:
> Any other ideas why sendfile() would get into a seek storm?
I can't really comment on the quality of the linux sendfile() implementation,
I've never looked at the code. However, a couple of general observations.
The seek storm happens because linux is trying to be "fair," where fair
means no one process get to starve another for I/O bandwidth.
The fastest way to transfer 100 100M files would be to send them one at a
time. The 99th person in line of course would percieve this as a very poor
implementation. The current sendfile implementation seems to live at the
other end of the extream.
It is possible to come up with a compromise behavior by limiting the
number of concurrent sendfiles running, and the maximum size they are
allowed to send in one squirt.
Thanks,
Jim
--
jlnance@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
next prev parent reply other threads:[~2006-01-22 14:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 21:53 sendfile() with 100 simultaneous 100MB files Jon Smirl
2006-01-21 2:22 ` Matti Aarnio
2006-01-21 3:43 ` Jon Smirl
2006-01-22 3:46 ` Benjamin LaHaise
2006-01-21 3:52 ` Phillip Susi
2006-01-22 14:24 ` Jim Nance [this message]
2006-01-22 17:31 ` Jon Smirl
2006-01-23 15:22 ` Jon Smirl
2006-01-24 16:30 ` Jon Smirl
2006-01-23 16:50 ` jerome lacoste
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=20060122142401.GA24738@SDF.LONESTAR.ORG \
--to=jlnance@sdf.lonestar.org \
--cc=jonsmirl@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.