- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Nonpaged pool problem
Operating System - OpenVMS
1754326
Members
2507
Online
108813
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
10-17-2007 09:43 AM
10-17-2007 09:43 AM
Re: Nonpaged pool problem
John,
AUTOGEN was designed in an age when resources, and particularly memory, was far more expensive than it is today. Although OpenVMS engineering has done some updating of the algorithms, they're still not completely up to date in terms of relative costs of resources. Sticking a finger in the air... they're probably appropriate for an Alpha system from about 1999 with up to 500MB of main memory and 20GB of disk space.
Also remember that AUTOGEN isn't so much a fine tuning tool, as one that will give you a conservative configuration that's guaranteed bootable. If your system is younger than my hypothetical 1999 Alpha, or with significantly more resources, you can well afford to be FAR more generous than AUTOGEN recommends.
If you don't have any apparent problems with what AUTOGEN has set, then let the sleeping dog lie, BUT if you're having any kind of issue, it's better to leapfrog the AUTOGEN recommendation to potentially avoid another round of error/increment/reboot.
In this case, even thinking about an NPAGEDYN difference of 10MB isn't worth your time. Consider the cost of that memory, and the proportion of your total. Round it up to the nearest single digit of precision and be done with it. Go 50MB or even 60MB. We're well past the days when "wasting" 10MB of RAM was a serious problem, especially for a key resource like NPAGEDYN
AUTOGEN was designed in an age when resources, and particularly memory, was far more expensive than it is today. Although OpenVMS engineering has done some updating of the algorithms, they're still not completely up to date in terms of relative costs of resources. Sticking a finger in the air... they're probably appropriate for an Alpha system from about 1999 with up to 500MB of main memory and 20GB of disk space.
Also remember that AUTOGEN isn't so much a fine tuning tool, as one that will give you a conservative configuration that's guaranteed bootable. If your system is younger than my hypothetical 1999 Alpha, or with significantly more resources, you can well afford to be FAR more generous than AUTOGEN recommends.
If you don't have any apparent problems with what AUTOGEN has set, then let the sleeping dog lie, BUT if you're having any kind of issue, it's better to leapfrog the AUTOGEN recommendation to potentially avoid another round of error/increment/reboot.
In this case, even thinking about an NPAGEDYN difference of 10MB isn't worth your time. Consider the cost of that memory, and the proportion of your total. Round it up to the nearest single digit of precision and be done with it. Go 50MB or even 60MB. We're well past the days when "wasting" 10MB of RAM was a serious problem, especially for a key resource like NPAGEDYN
A crucible of informative mistakes
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP