From: Harald Dunkel <harald.dunkel@aixigo.de>
To: linux-nfs@vger.kernel.org
Subject: Solaris NFSv3 client to Linux server
Date: Fri, 16 Oct 2009 09:08:56 +0200 [thread overview]
Message-ID: <4AD81C08.5020607@aixigo.de> (raw)
Hi folks,
I see a pretty poor NFSv3 performance for my Solaris10 machines
(sparc) connected to the Linux (amd64, 2.6.29.6) servers,
especially on removing a lot of files. Sample:
% time rm -rf linux-2.6.31.4/Documentation
real 0m45.268s
user 0m0.044s
sys 0m44.334s
Please note the high sys value. Using a Solaris 10 NFSv3 server
and the same client I get this instead:
% time rm -rf linux-2.6.31.4/Documentation
real 0m22.712s
user 0m0.029s
sys 0m0.330s
It is still not a brilliant time, but the sys value is much
closer to what one would expect.
The usual optimizations about attribute caching and wsize/rsize
etc. did not improve the poor performance. Not to mention that
NFSv4 is _much_ faster for both servers.
Of course I understand that this is a Solaris issue, but maybe
you have some insight? Did somebody investigate this?
Regards
Harri
reply other threads:[~2009-10-16 7:17 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=4AD81C08.5020607@aixigo.de \
--to=harald.dunkel@aixigo.de \
--cc=linux-nfs@vger.kernel.org \
/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.