From: Frank van Maarseveen <frankvm@frankvm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Greg Banks
<gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>,
Chuck Lever <chuck.lever@oracle.com>,
bfields@citi.umich.edu, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 4/5] NFSD: Remove NFSD_TCP kernel build option
Date: Tue, 5 Feb 2008 19:08:19 +0100 [thread overview]
Message-ID: <20080205180819.GA12916@janus> (raw)
In-Reply-To: <1202233839.8452.31.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Tue, Feb 05, 2008 at 12:50:39PM -0500, Trond Myklebust wrote:
>
> On Tue, 2008-02-05 at 16:50 +0100, Frank van Maarseveen wrote:
> > Last time I checked (around 2.6.22) writing large files on NFSv3 over
> > UDP was 20% faster compared to TCP (Gb LAN with one switch connecting
> > all machines).
> >
> > TCP and its timeout/retransmission behavior isn't always the best choice.
>
> If your environment has only 1 client working against a dedicated NFS
> server on a clean network, then that may indeed be the case, but as soon
> as you have more than 1 client, TCP almost always ends up outperforming
> UDP.
There are multiple clients (12 per physical server on average) but the
clients generally don't write (or read) at the same time. Anyway, I'll
keep this in mind.
--
Frank
next prev parent reply other threads:[~2008-02-05 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 0:04 [PATCH 4/5] NFSD: Remove NFSD_TCP kernel build option Chuck Lever
[not found] ` <20080205000442.18602.29035.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-02-05 0:19 ` Greg Banks
[not found] ` <47A7AB89.7020709-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05 0:19 ` Trond Myklebust
[not found] ` <1202170754.28484.57.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-05 0:29 ` Greg Banks
[not found] ` <47A7AE03.10401-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05 1:55 ` Chuck Lever
2008-02-05 5:49 ` Greg Banks
2008-02-05 6:05 ` Neil Brown
[not found] ` <47A7F8F3.3020907-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05 15:50 ` Frank van Maarseveen
2008-02-05 17:50 ` Trond Myklebust
[not found] ` <1202233839.8452.31.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-05 18:08 ` Frank van Maarseveen [this message]
2008-02-05 23:05 ` Greg Banks
[not found] ` <47A8EBC3.7050900-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org>
2008-02-05 23:08 ` J. Bruce Fields
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=20080205180819.GA12916@janus \
--to=frankvm@frankvm.com \
--cc=bfields@citi.umich.edu \
--cc=chuck.lever@oracle.com \
--cc=gnb-cP1dWloDopni96+mSzHFpQC/G2K4zDHf@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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