From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: nfs-server slowdown in 2.4.20-pre10 with client 2.2.19
Date: Tue, 15 Oct 2002 22:35:57 +0000 (UTC) [thread overview]
Message-ID: <aoi58d$hp3$1@forge.intermeta.de> (raw)
In-Reply-To: 20021015194538.10f54ef3.skraw@ithnet.com
Stephan von Krawczynski <skraw@ithnet.com> writes:
>On Mon, 14 Oct 2002 13:38:32 +1000
>Neil Brown <neilb@cse.unsw.edu.au> wrote:
>Hello Neil,
>hello Trond,
>> This night I will try to reduce rsize/wsize from the current 8192 down to
>> 1024 as suggested by Jeff.
>Ok. The result is: it is again way slower. I was not even capable to transfer 5
>GB within 18 hours, that's when I shot the thing down.
>Anything else I can test?
nfs v2 or v3? tcp or udp? I assume nfs v3, udp and 100 Mbit switched
network between your hosts and no firewalls, routers or something like
this.
Could you post a small (some ten lines or so) tcp dump of a data transfer?
I had a hell of a time with a) a firewall dropping fragments; b) a
trunked network connection where one VLAN "pushed" another running the
NFS traffic off the trunk (Also vice versa, letting 97 Mbit/sec NFS
traffic pushing almost everything else from the trunk but this is
obviously not your problem. :-) )
If lowering the blocksize speeds up your transfers, dropping fragments
could be the problem (shorter blocks result in less fragments per
packets and increase the chance that all fragments make it over the
connection).
Could you watch the Ip: InDiscards ReasmTimeout ReasmReqds ReasmFails
and Udp: InErrors counters in /proc/net/snmp. Is any of them steadily
increasing?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2002-10-15 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 15:21 nfs-server slowdown in 2.4.20-pre10 with client 2.2.19 Stephan von Krawczynski
2002-10-13 23:03 ` Neil Brown
2002-10-14 2:54 ` Stephan von Krawczynski
2002-10-14 3:38 ` Neil Brown
2002-10-14 14:36 ` Stephan von Krawczynski
2002-10-14 23:31 ` Jeff Lightfoot
2002-10-15 17:45 ` Stephan von Krawczynski
2002-10-15 22:35 ` Henning P. Schmiedehausen [this message]
2002-10-16 3:36 ` Neil Brown
2002-10-14 13:43 ` Trond Myklebust
2002-10-14 4:35 ` Jeff Lightfoot
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='aoi58d$hp3$1@forge.intermeta.de' \
--to=hps@intermeta.de \
--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 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).