From: Willy Tarreau <email@example.com>
To: Chuck Lever <firstname.lastname@example.org>
Cc: Marcelo Tosatti <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>
Subject: Re: [PATCH] 2.4 read ahead never reads the last page in a file
Date: Sat, 6 Dec 2003 09:20:11 +0100 [thread overview]
Message-ID: <20031206082011.GD11325@alpha.home.local> (raw)
I've run 2.4.23 both vanilla and patched, and I confirm a win on NFS reads.
I tested from 1 to 6 parallel reads consisting of md5sum of kernel includes :
time find include -type f | xargs md5sum >/dev/null &
Results below :
processes 2.4.23 2.4.23-patched
1 11.5 11.45
2 12.82 12.68
3 14.7 14.4
4 17.8 17.3
5 21.5 21.0
6 25.7 25.0 => server is saturated 100% sys
7 29.3 29.0 => server is saturated 100% sys
Fileset contain 7346 files totalizing 29952 kB.
So there's a gain of nearly 3% in the best case (6 processes). Not bad.
I suspect that I could also gain slightly more by patching the server too.
prev parent reply other threads:[~2003-12-06 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 23:10 [PATCH] 2.4 read ahead never reads the last page in a file Chuck Lever
2003-12-05 1:32 ` Andrea Arcangeli
2003-12-05 15:51 ` Marcelo Tosatti
2003-12-05 1:54 ` Mike Fedyk
2003-12-06 8:20 ` Willy Tarreau [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).