From: "Patrice Seyed" <apseyed@bu.edu>
To: <nfs@lists.sourceforge.net>
Cc: "'Patrice Seyed'" <apseyed@bu.edu>
Subject: ReasmFails increases / NFS performance on Linux Cluster
Date: Sat, 14 Aug 2004 03:46:44 -0400 [thread overview]
Message-ID: <001501c481d2$d8900950$6701a8c0@psyche1> (raw)
We have 1 ibm x345 as a management node, and 1 ibm x35 as a storage =
node,
(both dual cpu 2.8 xeon and 2.5gb memory) which is fiber channeled to a =
Raid
5 array with ~900 GB usable. Then we have 10 IBM BladeCenters which =
contain
14 blades per chassis except the last one (has 8). So 134 nodes with =
dual
xeon at 2.8Ghz, mostly with 1GB ram and 20 with 2GB.
All nodes including x345s are set to 1000/full and cabled into a 3750
Cataylst. Bear in mind each BladeCenter chassis include a switch module,
which is also set to 1000/full.
In testing dd writes from /dev/zero to an nfs mount and back in a large
number of batch jobs, I'm seeing high load on the storage node and heavy
slowdowns for example for ssh login, df, or ls on the head node.=20
In my attempt to tune the storage node, I have tried 32k and now 8k
(rsize,wsize in autofs) with no improvement in the slowness. Other
parameters I am using are hard,intr,noatime,retrans=3D20,timeo=3D25. I =
am
currently running 64 nfsd daemons. Also I now have ipfrag_low_thresh and
ipfrag_high_thread both set to 1045876. When I had doubled the default
values for these settings a few weeks ago, it appeared to solve I/O =
errors
that were appearing in the logs for many of the nodes. Still now the
ReasmFails value in /proc/net/snmp steadily increases (for 8k or 32k) =
when I
submit a moderate number of jobs (20-40) that are heavy on I/O.
More info (on the storage node):
$ netstat -s | less
Ip:
226750504 total packets received
0 forwarded
501200 incoming packets discarded
164658619 incoming packets delivered
161895650 requests sent out
5006 fragments dropped after timeout
80794698 reassemblies required
13723023 packets reassembled ok
126665 packet reassembles failed
2858536 fragments received ok
14006786 fragments created
Udp:
159845714 packets received
142 packets to unknown port received.
501200 packet receive errors
152909713 packets sent
I welcome any suggestions or recommendations.
Regards,
=20
Patrice Seyed
Linux System Administrator - SIG
RHCE, SCSA
Boston University School of Medicine
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-08-14 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 7:46 Patrice Seyed [this message]
2004-08-14 9:23 ` ReasmFails increases / NFS performance on Linux Cluster Olaf Kirch
2004-08-15 21:52 ` Patrice Seyed
[not found] <E1BwYLA-0004on-C0@sc8-sf-list2.sourceforge.net>
2004-08-16 12:54 ` Joshua Baker-LePain
2004-08-16 21:05 ` Patrice Seyed
2004-08-17 8:05 ` Olaf Kirch
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='001501c481d2$d8900950$6701a8c0@psyche1' \
--to=apseyed@bu.edu \
--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.