mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Caleb Epstein <cae@bklyn.org>
To: linux-kernel@vger.kernel.org
Subject: NFS client code slow in 2.4.3
Date: Tue, 3 Apr 2001 14:56:15 -0400	[thread overview]
Message-ID: <20010403145615.C1049@hagrid.bklyn.org> (raw)


	I am having problems with timeouts and generaly throughput in
	the 2.4.3 NFS client side code which are not present in the
	2.4.2 kernel running in the same configuraiton on the same
	hardware.  The machines are on a 100 Mbit switched local
	network with essentially no other trafic.

	In both cases, testing against a 2.4.3 NFS server (using
	knfsd).  My tests involved using "dd" to read a large file on
	an NFS mounted directory and running the "connectathon" NFS
	test suite.

	When I boot my client machine with 2.4.3, reading a 327 Mbyte
	file over NFS takes on the order of 5-6 minutes to complete.
	If I run the same command witrh the client running kernel
	2.4.2, the command completes in about 1 minute.

	Running the "cthon01" test suite, the 2.4.3 client machine
	basically hangs in the "read + write" test section and I
	didn't bother waiting for it to finish.  Again, when switching
	back to 2.4.2, the client runs through the tests quite
	quickly.

	From my tests I'm pretty convinced that something in either
	the NFS client code or the networking layer has changed which
	has drastically reduced NFS client speeds in 2.4.3.

	Is this a known problem?  Can I provide any additional
	information to help debug it?

-- 
cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg.

             reply	other threads:[~2001-04-03 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-03 18:56 Caleb Epstein [this message]
2001-04-03 19:08 ` Caleb Epstein
2001-04-03 20:00   ` Trond Myklebust

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=20010403145615.C1049@hagrid.bklyn.org \
    --to=cae@bklyn.org \
    --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

all inboxes | Powered by JetHome®