From: Alkis Georgopoulos <alkisg@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: rsize,wsize=1M causes severe lags in 10/100 Mbps, what sets those defaults?
Date: Thu, 19 Sep 2019 10:29:40 +0300 [thread overview]
Message-ID: <80353d78-e3d9-0ee2-64a4-cd2f22272fbe@gmail.com> (raw)
Hi, in any recent distribution that I tried, the default NFS wsize/rsize
was 1 MB.
On 10/100 Mbps networks, this causes severe lags, timeouts, and dmesg
fills with messages like:
> [ 316.404250] nfs: server 192.168.1.112 not responding, still trying
> [ 316.759512] nfs: server 192.168.1.112 OK
Forcing wsize/rsize to 32K makes all the problems disappear and NFS
access more snappy, without sacrificing any speed at least up to gigabit
networks that I tested with.
I would like to request that the defaults be changed to 32K.
But I didn't find out where these defaults come from, where to file the
issue and my test case / benchmarks to support it.
I've initially reported it at the klibc nfsmount program that I was
using, but this is just using the NFS defaults, which are the ones that
should be amended. So initial test case / benchmarks there:
https://lists.zytor.com/archives/klibc/2019-September/004234.html
Please Cc me as I'm not in the list.
Thank you,
Alkis Georgopoulos
next reply other threads:[~2019-09-19 7:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 7:29 Alkis Georgopoulos [this message]
2019-09-19 15:08 ` rsize,wsize=1M causes severe lags in 10/100 Mbps, what sets those defaults? Trond Myklebust
2019-09-19 15:58 ` rsize,wsize=1M causes severe lags in 10/100 Mbps Alkis Georgopoulos
2019-09-19 16:11 ` Trond Myklebust
2019-09-19 19:21 ` Alkis Georgopoulos
2019-09-19 19:51 ` Trond Myklebust
2019-09-19 19:57 ` Alkis Georgopoulos
2019-09-19 20:05 ` Trond Myklebust
2019-09-19 20:20 ` Alkis Georgopoulos
2019-09-19 20:40 ` Trond Myklebust
2019-09-19 21:19 ` Daniel Forrest
2019-09-19 21:42 ` Trond Myklebust
2019-09-19 22:16 ` Daniel Forrest
2019-09-20 9:25 ` Alkis Georgopoulos
2019-09-20 9:48 ` Alkis Georgopoulos
2019-09-20 10:04 ` Alkis Georgopoulos
2019-09-21 7:52 ` Alkis Georgopoulos
2019-09-21 7:59 ` Alkis Georgopoulos
2019-09-21 11:02 ` Alkis Georgopoulos
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=80353d78-e3d9-0ee2-64a4-cd2f22272fbe@gmail.com \
--to=alkisg@gmail.com \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).