All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: RedHat 8.0 nfs
Date: Thu, 20 Mar 2003 15:28:04 -0500	[thread overview]
Message-ID: <3E7A2454.7070003@RedHat.com> (raw)
In-Reply-To: D38AFB3080F3D311807300B0D0203E53033A94CB@MERCURY



pwitting@Cyveillance.com wrote

>So what guidelines should I use in setting these values? RH 7.3 limited me
>to 128 threads (I got nervous using ALL the possible threads and backed it
>off), RH8 supports more. Judging by the /proc, there is a significant amount
>of time where all threads are in use, even at 120
>
Not knowing anything about the size of your machines, the type of
traffic, your network, or the history of what works and what doesn't
makes it  tough to give a decisive answer... So I can only suggest
crank it up until it hurts. :-) Theoretically RH8.0 can support up to 32000
processes and 1200 threaded processes, so its all dependent on the size
of your machine (i.e. number of cpus, amount of memory, type of storage)
Experimentation is your friend...

>
>Also, what would be a good number for NFS_QS? Both rmem.default and rmem.max
>will be set to this number; should it be a multiple of threads? Say
>something like smallest binary power (2^n) greater than 1500 (MTU size) *
>$RPCNFSDCOUNT 
>
>So 120*1500 = 180,000 > 262,144, but
>   220*1500 = 330,000 > 524,288
>  
>
Again this dependent on how much memory you have...

>Or should RPCNFSDCOUNT itself be some power of 2?
>
I don't think it matters or at least I don't see why it should...

>
>And while we're on the subject of RedHat, any idea how up to date the NFS
>code is in their latest kernel (2.4.18-27)? Its nice relying on their bug
>testing/security/useful_patches/fixes, but I saw a significant performance
>increase by migrating to 2.4.20 a few months ago. I also ran into a wall
>trying to integrate the Q-Logic FC drivers I need for some of my systems.
>  
>
Unfortunately, we not able to get in some of latest performance 
enhancements
due to our QA cycle...

SteveD.





-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC.  
Does your code think in ink? You could win a Tablet PC. 
Get a free Tablet PC hat just for playing. What are you waiting for? 
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-03-20 20:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 16:52 RedHat 8.0 nfs pwitting
2003-03-20 20:28 ` Steve Dickson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-24 18:42 pwitting
2003-03-25 22:50 ` David Dougall
2003-03-25 23:19   ` Trond Myklebust
2003-03-25 23:53   ` Neil Brown
2003-03-25 23:27 pwitting
2003-03-26 18:34 pwitting
2003-03-26 23:43 ` Neil Brown

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=3E7A2454.7070003@RedHat.com \
    --to=steved@redhat.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.