From: Frank Steiner <fsteiner-mail1@bio.ifi.lmu.de>
To: nfs@lists.sourceforge.net
Subject: Terrible performance between 2.6.16 and 2.6.5
Date: Thu, 30 Nov 2006 12:51:45 +0100 [thread overview]
Message-ID: <456EC5D1.9050008@bio.ifi.lmu.de> (raw)
Hi,
I just upgraded our NFS server from SuSE 9.2 (kernel 2.6.8) to SuSE 10.1
(2.6.16.21). We have some SLES 9 (2.6.5) and some SLES 10 (2.6.16) clients
acessing the NFS server.
When the server ran 2.6.8, the performance was always fine. After upgrading
the SLES 10 clients still have nice performance, but the SLES 9 clients
are terrible.
Here's a test call I'm doing:
find /mnt/tmp/i586/9/SuSE-updates/ -name \*.rpm -exec rpm -qp {} \;
It just queries all the rpm packages for their name.
When I call this on a SLES 10 client I can monitor the network traffic
on the server lies between 200k and some little peaks at 1.5M.
Calling it on a SLES9 client looks fine at first, then after some RPMs
the network traffic raises to about 20-30 MB/sec! Guess what the server
says when 30 clients search for new RPMs with an algorithm similar to this.
When I call the "find" a second time on the same SLES 9 clients it runs
fine for some longer time, like it had cached the accesses or if it had some
buffer that would fill and then slow the read down.
On all clients we mount with "ro,tcp,hard,rsize=16384,wsize=16384".
Changing sync/async on the server and the clients didn't help.
Are there any known issues? Any ideas how I could debug this? We
can't throw away SLES 9 on these clients, so I need to solve this :-(
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2006-11-30 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 11:51 Frank Steiner [this message]
2006-11-30 14:24 ` Terrible performance between 2.6.16 and 2.6.5 Roger Heflin
2006-11-30 15:18 ` Frank Steiner
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=456EC5D1.9050008@bio.ifi.lmu.de \
--to=fsteiner-mail1@bio.ifi.lmu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox