All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jehan.procaccia" <jehan.procaccia@int-evry.fr>
To: DUPRE Julien <julien.dupre-renexter@renault.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: how many nfs  thread needed
Date: Fri, 25 Feb 2005 19:17:07 +0100	[thread overview]
Message-ID: <421F6BA3.7050304@int-evry.fr> (raw)
In-Reply-To: <01e101c51b2a$07a027c0$bef5dc0a@corp.noxiane.net>

DUPRE Julien wrote:

> Hi,
>  
> i'm looking for tunning my NFS configuration on a RedHAt 7.3 ( my 
> client are in ES3)
> for increase my performance.
>  
> I reading some docs but i need help for chose a good value
>  
> balsa-b#  grep th /proc/net/rpc/nfsd 
> th 84 203258 22002.912 7932.515 4694.613 6721.031 4074.175 605.630 
> 396.916 376.582 501.927 2942.259
> balsa-b#
>  

you've already got 84 Threads and they all seem quite busy ! I'am not 
sure, but for me unless the last numbers above are near to zero second 
of use , you should increase the number of threads -> up to 128 in your 
case ? but will the server support it ? you seem to have many clients ?
have a look at:
http://marc.theaimsgroup.com/?l=linux-nfs&m=102824853219024&w=2
http://www.int-evry.fr/s2ia/user/procacci/Doc/NFS/nfs.html#htoc8

>
> I think i need to change my number of thread nfsd but how many ?
>  
>  
> Thanks in advance
>  
>  
>  
>  
>  
>  
>  
>  
>
>  
>
>------------------------------------------------------------------------
>
>-- Disclaimer ------------------------------------
>Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme.
>***
>This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system.
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-02-25 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 11:06 how many nfs thread needed DUPRE Julien
2005-02-25 18:17 ` jehan.procaccia [this message]
2005-03-02 10:25   ` DUPRE Julien

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=421F6BA3.7050304@int-evry.fr \
    --to=jehan.procaccia@int-evry.fr \
    --cc=julien.dupre-renexter@renault.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.