From: Peter Staubach <staubach@redhat.com>
To: Wendy Cheng <s_wendy_cheng@hotmail.com>
Cc: nfs@lists.sourceforge.net, wcheng@redhat.com
Subject: Re: [NFS] NFS Digest, Vol 18, Issue 70 (NFS performance problems)
Date: Tue, 20 Nov 2007 16:17:11 -0500 [thread overview]
Message-ID: <47434ED7.4010100@redhat.com> (raw)
In-Reply-To: <BAY104-W43766F661E50E7FFCDA8EBA7F0-MsuGFMq8XAE@public.gmane.org>
Wendy Cheng wrote:
>
>> top - 15:50:56 up 20 days, 1:33, 9 users, load average: 3.42, 2.95, 2.38
>>
>> 19200 geo0501 15 0 75076 5224 3480 S 2 0.1 0:07.94 smbd
>> 2336 root 10 -5 0 0 0 S 1 0.0 57:07.70 kjournald
>> 2334 root 10 -5 0 0 0 S 1 0.0 33:19.89 kjournald
>> 2279 root 10 -5 0 0 0 S 0 0.0 15:10.98 md0_raid1
>> 2283 root 10 -5 0 0 0 S 0 0.0 24:45.79 md1_raid1
>> 3935 root 15 0 0 0 0 S 0 0.0 14:04.25 nfsd
>> 3943 root 15 0 0 0 0 S 0 0.0 14:18.43 nfsd
>> 3947 root 15 0 0 0 0 S 0 0.0 13:57.06 nfsd
>> 8325 ed0127 15 0 75044 4812 3264 S 0 0.1 0:01.29 smbd
>>
>
> Intuitively (based on ext3's journal threads info above) I would suspect this is due to the change of the export default option from "async" to "sync" between 2.6.9 and 2.6.18 kernels. So go to your /etc/exports file and explicitly set the export option to "async" to see whether you can get the performance back.
>
> e.g. changes "/server *(rw)" to "/server *(async, rw)".
While this may or may not restore your performance aspects, it
is not safe to make this change. The change was made for a
reason.
Please any and all other possibilities before making this change.
It is not free.
Thanx...
ps
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2007-11-20 21:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.194659.1195581701.26582.nfs@lists.sourceforge.net>
2007-11-20 20:22 ` [NFS] NFS Digest, Vol 18, Issue 70 (NFS performance problems) Wendy Cheng
[not found] ` <BAY104-W43766F661E50E7FFCDA8EBA7F0-MsuGFMq8XAE@public.gmane.org>
2007-11-20 21:17 ` Peter Staubach [this message]
2007-11-20 21:23 ` Wendy Cheng
2007-11-21 16:04 ` Chuck Lever
2007-11-26 3:28 ` Wendy Cheng
2007-11-26 4:41 ` Trond Myklebust
2007-11-26 5:02 ` J. Bruce Fields
[not found] ` <18254.19187.470275.538680@notabene.brown>
[not found] ` <18254.19187.470275.538680-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2007-11-29 5:30 ` Trond Myklebust
[not found] ` <1196314230.7950.42.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2007-11-30 16:27 ` Wendy Cheng
2007-12-03 20:31 ` J. Bruce Fields
2007-12-03 21:13 ` Wendy Cheng
2007-12-03 21:30 ` J. Bruce Fields
2007-12-03 21:38 ` J. Bruce Fields
2007-12-03 21:49 ` Wendy Cheng
2007-12-03 22:07 ` J. Bruce Fields
2007-11-27 18:40 ` Rui Pedro Mendes Salgueiro
[not found] ` <20071127184050.GA13791-/uZbGGhPd8Gmv2Aub4FSgw@public.gmane.org>
2007-11-28 1:50 ` Chuck Lever
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=47434ED7.4010100@redhat.com \
--to=staubach@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=s_wendy_cheng@hotmail.com \
--cc=wcheng@redhat.com \
/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