From: "poczta.dotcom.pl" <myciel@dotcom.pl>
To: <nfs@lists.sourceforge.net>
Subject: nfs performance problem
Date: Tue, 5 Nov 2002 19:03:43 +0100 [thread overview]
Message-ID: <005b01c284f5$ae1d6090$640a010a@winda> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Hi All
I have really slow working nfs.
Server is build on:
- dual pentium Xeon 2GHz,
- 2 3ware 7500 controllers,
- raid 5 on 7 160GB discs on controler 1
- raid 5 on 6 160GB disks on cotroller 2
Serwer is used for ~500k maildirs,
all clients (~20) are freebsd boxes, when nfs transfer is around 1MB/s for writing and 1.5MB/s for reading
listing user directories even with very few file stakes up to 15 seconds.
I tried nfs-ALL patch, but it didn' t help.
I run 256 nfs daemons,
echo 2097152 > /proc/sys/net/core/rmem_max
echo 2097152 > /proc/sys/net/core/rmem_default
nsfstat output:
Server rpc stats:
calls badcalls badauth badclnt xdrcall
25271043 17885061 0 17885061 0
Server nfs v3:
null getattr setattr lookup access readlink
25 0% 1159 0% 89718 0% 11702395 46% 10953437 43% 34868 0%
read write create mkdir symlink mknod
925727 3% 226250 0% 44964 0% 1089 0% 2299 0% 0 0%
remove rmdir rename link readdir readdirplus
35040 0% 42 0% 121064 0% 535 0% 534720 2% 0 0%
fsstat fsinfo pathconf commit
585179 2% 36 0% 0 0% 12493 0%
mount over tcp gives frequent errors on freebsd clients side:
kernel: nfs send error 32 from nfs server xxx.xxx.xxx.xxx:/export
thanks for any help,
rafal
[-- Attachment #2: Type: text/html, Size: 3748 bytes --]
next reply other threads:[~2002-11-05 18:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 18:03 poczta.dotcom.pl [this message]
2002-11-05 19:17 ` nfs performance problem Ragnar Kjørstad
2002-11-05 19:55 ` poczta.dotcom.pl
2002-11-05 20:22 ` Matt Heaton
2002-11-05 20:39 ` Benjamin LaHaise
2002-11-05 20:46 ` Matt Heaton
2002-11-05 21:24 ` Benjamin LaHaise
2002-11-05 23:32 ` Ragnar Kjørstad
2002-11-06 8:59 ` myciel
2002-11-06 10:16 ` Ragnar Kjørstad
2002-11-06 11:46 ` myciel
-- strict thread matches above, loose matches on Subject: below --
2002-11-05 20:56 Lever, Charles
2002-11-05 22:09 Lever, Charles
2002-11-06 17:08 pwitting
2002-11-07 15:19 Baker, Byran
2002-11-07 15:49 ` Matt Heaton
2002-11-07 17:32 ` Ragnar Kjørstad
2007-10-25 13:10 Andreas Schuldei
2007-10-25 13:53 ` Bernd Schubert
2007-10-27 9:25 ` Andreas Schuldei
2007-10-25 15:25 ` Chuck Lever
2007-10-25 19:34 ` Andreas Schuldei
2007-10-26 14:18 ` Chuck Lever
2007-10-26 17:01 ` Talpey, Thomas
2007-10-27 1:35 ` dean hildebrand
[not found] ` <c5befdd30710261835q50d34026h4dad32090db8a084@mail.gmail.co m>
2007-10-29 12:59 ` Talpey, Thomas
2007-10-25 14:39 Andreas Schuldei
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='005b01c284f5$ae1d6090$640a010a@winda' \
--to=myciel@dotcom.pl \
--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