All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: AK <amithl_prem@yahoo.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Performance: NFS v3  mounting with 'noac' option
Date: Wed, 07 Mar 2007 17:39:28 -0500	[thread overview]
Message-ID: <45EF3F20.5060300@redhat.com> (raw)
In-Reply-To: <141076.2067.qm@web56606.mail.re3.yahoo.com>

AK wrote:
> --- Peter Staubach <staubach@redhat.com> wrote:
>
>   
>>> We have multiple file systems begin mounted from
>>>       
>> the
>>     
>>> same NFS server. One of our user's application
>>> requires to mount the file system with 'noac'
>>>       
>> option. 
>>     
>>>   
>>>       
>> What about this application requires that the "noac"
>> option be used?
>>     
>   application is romio with mpich2 ...
>  
>   

Sorry, I'm not familiar with those.  What about either one of those
require "noac" semantics?

>> One of the impacts of using the "noac" option is
>> much more network
>> traffic and it will be composed of small packets. 
>> If the server is
>> busy handling all of the additional GETATTR
>> requests, then it won't
>> be handling other requests.  The client will also be
>> a bit busier
>> with generating the additional requests, instead of
>> just doing what
>> might be considered more useful work.
>>
>> So, there should be no direct impact to other
>> mounted file systems.
>> However, there may be indirect impacts.
>>     
>
> indirect impacts: can you please elaborate on this.

I thought that I did.  :-)

If the system is busy handling the "noac" aspects of one file system,
then it isn't doing something else on one of the other file systems.
System resources are limited and using up more of them for one thing
leaves less for others.

       ps

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-03-07 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 14:54 Performance: NFS v3 mounting with 'noac' option AK
2007-03-07 17:55 ` Peter Staubach
2007-03-07 21:32   ` AK
2007-03-07 22:39     ` Peter Staubach [this message]
2007-03-08 14:55       ` AK
2007-03-08 16:13         ` Peter Staubach
2007-03-08 16:19           ` Talpey, Thomas
2007-03-08 16:52             ` AK
2007-03-08 17:06               ` Talpey, Thomas

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=45EF3F20.5060300@redhat.com \
    --to=staubach@redhat.com \
    --cc=amithl_prem@yahoo.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.