- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: num_nfsd
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 03:47 PM
05-11-2005 03:47 PM
Thank you in advance for every reply
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 04:09 PM
05-11-2005 04:09 PM
Re: num_nfsd
man nfsd
"nfsd starts the NFS server daemons that handle client file system requests (see nfs(7)). num_nfsd is the suggested number of file system request daemons that will start. One daemon will be started to support the kernel threads servicing TCP requests, and multiple additional daemons will be started to service UDP requests. At system boot time, num_nfsd is defined by the NUM_NFSD variable in the /etc/rc.config.d/nfsconf file. When the UDP nfsds are launched, the kernel will automatically round up num_nfsd to be a multiple of the number of active CPU's in the system.
On a system with 16 active CPU's the following command:
/usr/sbin/nfsd 30
will result in a total 33 nfsds being launched. For UDP requests, the kernel rounds-up the requested num_nfsd value to be a multiple of the number of active CPU's in the system, resulting in 32 UDP daemons. One additional daemon will be launched to support kernel TCP threads, resulting in a total of 33 daemons.
The following command:
/usr/sbin/biod 16
will result in a total of 16 block I/O daemons being launched. The number of active CPU's in the system has no effect on the number of biods started."
So it doesnot mean that you can connect 16 client machines, but you can have each daemon handling one request (file system opration) at a time.
Regards,
Naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 09:15 PM
05-11-2005 09:15 PM
Re: num_nfsd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 09:27 PM
05-11-2005 09:27 PM
SolutionYou may need a look at
http://docs.hp.com/en/1435/NFSPerformanceTuninginHP-UX11.0and11iSystems.pdf
Page 41 onwards talks about nfsd daemons.
There are numerous factors which determines this. ttcp and netperf are some good tools to derive client server statistics.
With best wishes,
Naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2005 10:44 PM
05-11-2005 10:44 PM