From: Brett Petrusek <brettp@aspsys.com>
To: nfs@lists.sourceforge.net
Subject: IA64 Server / IA32 Client Problem
Date: Wed, 20 Jul 2005 16:37:18 -0600 [thread overview]
Message-ID: <42DED21E.4010608@aspsys.com> (raw)
I'm not sure if this is a bug or what, but I am experiencing severe
performace problems between an IA64 NFS server and IA32 NFS client. I
have tried every combination of socket buffer sizes as well as many
other nfs options, but none of them seem to have any effect. I have
tried RHEL21 to RHEL3U5 with all of these socket combos and still no
difference. The command I am running is:
time dd if=/dev/zero of=/scratch_dir_across_nfs bs=1M count=128
Between two IA32 machines this takes 4-5 seconds. Between IA64 server
and IA32 client this takes on the order of minutes. Network performance
has been eliminated from the equation as after kernel tuning we have
achieved consistent 94% of peak tcp throughput and 95.7% of peak udp
throughput on our GigE network. This is both between IA32 and IA64
systems.
Let me know if there is an other info I should provide to help
troubleshoot this problem.
Any help is appreciated.
Thanks, Brett P
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-07-20 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 22:37 Brett Petrusek [this message]
2005-07-21 19:29 ` IA64 Server / IA32 Client Problem Dan Stromberg
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 14:36 IA64 Server / IA32 Client problem Lever, Charles
2005-08-02 15:27 ` Olaf Kirch
2005-08-02 15:37 ` Brett Petrusek
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=42DED21E.4010608@aspsys.com \
--to=brettp@aspsys.com \
--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.