All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: nfs@lists.sourceforge.net
Subject: client: 2.6.7 client much slower than 2.4.26
Date: Thu, 1 Jul 2004 23:18:12 +0200	[thread overview]
Message-ID: <200407012318.18934.bernd-schubert@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2260 bytes --]

Hi,

I'm currently testing 2.6.7 on one of our clients and the nfs transfer is much 
slower than when the same system is running 2.4.X

Well, the usual suggestion probably would be to run nfs over tcp now, but tcp 
is already enabled (from /proc/mounts):

taylor:/worka /mnt/test nfs 
rw,v3,rsize=32768,wsize=32768,hard,tcp,lock,addr=taylor 0 0

benchmarks:

copy a file to the server (2.6.7): ~ 3MB/s
copy a file to the server (2.4.26): ~ 9MB/s

copy a file from the server (2.6.7): ~ 3MB/s
copy a file from the server (2.4.26): ~ 11MB/s

The filesize was 300MB.


Here's the nfsstat output:

euklid:~# nfsstat
Client rpc stats:
calls      retrans    authrefrsh
385466     0          0
Client nfs v2:
null       getattr    setattr    root       lookup     readlink
0       0% 27475  66% 231     0% 0       0% 3963    9% 161     0%
read       wrcache    write      create     remove     rename
8303   20% 0       0% 560     1% 171     0% 198     0% 42      0%
link       symlink    mkdir      rmdir      readdir    fsstat
45      0% 0       0% 3       0% 3       0% 129     0% 2       0%

Client nfs v3:
null       getattr    setattr    lookup     access     readlink
0       0% 56851  16% 1047    0% 17711   5% 36670  10% 936     0%
read       write      create     mkdir      symlink    mknod
73640  21% 149802 43% 629     0% 86      0% 1       0% 0       0%
remove     rmdir      rename     link       readdir    readdirplus
701     0% 105     0% 279     0% 36      0% 464     0% 1557    0%
fsstat     fsinfo     pathconf   commit
260     0% 18      0% 0       0% 3387    0%


I already tried to reduce rsize and wsize up to 1024, but this didn't change 
anything.

This happens to two different servers, one server is running 2.6.7 and has 
Gigabit connection to the switch. The other server is running 2.4.25 and only 
has a 100MBit connection. All of our clients have 100MBit connections.

So I really thing this is a client problem. Well, the client is not the 
fastest of our systems (PII 450), but with 2.4.X it has the usual speed. Its 
also interesting top is showing that the rpciod is taking all cpu-time when 
copying a file to the server.

Any ideas whats going on?

Thanks,
	Bernd

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-07-01 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 21:18 Bernd Schubert [this message]
2004-07-01 21:43 ` client: 2.6.7 client much slower than 2.4.26 Trond Myklebust
2004-07-01 22:32   ` Bernd Schubert

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=200407012318.18934.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --cc=nfs@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.