- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vx-ninode again
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
тАО01-31-2005 12:22 PM
тАО01-31-2005 12:22 PM
Eric recommends setting vx_ninode to 20k - 30k as a start. I want my first setting to be permanent for a long time! After writing this quick script on my production system :
bdf -i |grep -v "/stand" |awk '{print $6}' |grep -v iused |awk '{sum+=$1;printf("sum: %d\n",sum)}'
I get a total in use value of 234340. Is this the value I want to use to trend my future setting other than the default 0?
thx a bunch!
derek : )
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2005 02:32 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 01:45 AM
тАО02-01-2005 01:45 AM
Re: vx-ninode again
I concur.
The default value of 0 can lead to values of more than 1/4 million on large RAM systems.
I've been advised by experts that one *never* needs more than 40k in real life.
This is definitely one of those parms that *should* be tuned properly out-of-the-box, but isn't.
My $0.02,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 02:03 AM
тАО02-01-2005 02:03 AM
Re: vx-ninode again
even though when I echo this parameter I get
echo "vxfs_ninode /D" |adb -k /stand/vmunix /dev/kmem
240640?????
why is 20-30k recommended considering this number above and has anyone been in the situation before? has anyone changed it w/out negative results?
thank you,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 02:18 AM
тАО02-01-2005 02:18 AM
Re: vx-ninode again
The number drawn from the kernel is the *max* number of open vx inode table entries allowed. So think about just how *many* files you'll ever have open. I doubt you'll ever have more than 40k at any one time. So why not save the kernel memory & set the value to a realistic value?
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 02:51 AM
тАО02-01-2005 02:51 AM
Re: vx-ninode again
So the 234340 number can be ignored and taken for granted? Is the number in any way useful?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 04:37 AM
тАО02-01-2005 04:37 AM
Re: vx-ninode again
Consider 2 things:
A) What's the memory "cost" of the cache table size?
B) What's the CPU "cost" of searching an unnecessarily large table?
Those "costs" are what I'm pointing out. You don't need a huge table for exactly those two reasons. Set it to 40k & forget it.
My 2 cents,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2005 04:41 AM
тАО02-01-2005 04:41 AM
Re: vx-ninode again
then why does it flucuate?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-10-2005 10:52 AM
тАО02-10-2005 10:52 AM
Re: vx-ninode again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2005 04:27 PM
тАО04-05-2005 04:27 PM