From: Nicolas CROS <Nicolas.Cros@cls.fr>
To: nfs@lists.sourceforge.net
Cc: Christophe Kersuzan <ckersuzan@cls.fr>,
Lionel Cazaux <lionel.cazaux@cadrus.fr>
Subject: Solaris Server/Linux Clients NFS Performance Problem
Date: Thu, 28 Mar 2002 17:47:50 +0100 [thread overview]
Message-ID: <3CA34936.ED451E6E@cls.fr> (raw)
Hello,
We have severe performances problems on our configuration :
. a NFS server running on Solaris2.8=20
. several NFS clients running Linux (Redhat, Mandrake) or
Solaris 2.7
For testing purpose, i copied a 268MB from /dev/zero to
the NFS mounted FS. Here's the results :
NFS Client NFS Server Time
linux linux 36s
linux solaris 208s
solaris solaris 26s
solaris linux 47s
We do not experiment problems when file transfer are done without
NFS (rcp for example), neither when reading files.
I tried to play with mount options without success (-o -w=3D , -o tcp)
Any ideas welcome !!
--
Nicolas.Cros@cls.fr CLS
Administrateur Syst=E8me 8-10 rue Herm=E8s
tel 05.61.39.48.81 Parc Technologique du Canal
fax 05.61.39.48.40 31526 Ramonville St Agne cedex, France
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2002-03-28 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CA34936.ED451E6E@cls.fr \
--to=nicolas.cros@cls.fr \
--cc=ckersuzan@cls.fr \
--cc=lionel.cazaux@cadrus.fr \
--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