- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: locakble memory in dmesg
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-12-2010 05:54 AM
тАО01-12-2010 05:54 AM
locakble memory in dmesg
rx6600 with 256 gb memory, running Oracle and want to use as much as possible for SGA.
So far I can only use 200 gb for SGA, and when running dmesg it says:
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 268404004 Kbytes, lockable: 204443204 Kbytes, available: 232680536 Kbytes
Is the "locakble" value the reason I can't use more than 200 Gb for SGA, and if so is there a way to "change" this ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 06:08 AM
тАО01-12-2010 06:08 AM
Re: locakble memory in dmesg
No lockable is not the reason you can't make the SGA big enough.
More likely it has to do with use of memory for other things.
Check the kernel parameter dbc_max_pct.
By default it takes 50% of memory for a buffer cache. This has been known on 11.23 to improve Oracle performance, however it might be more efficient to reduce this figure and free up resources for the SGA.
Note this parameter has been renamed on HP-UX 11.31 and you are not indicating the OS, which matters in providing you an accurate answer.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 06:13 AM
тАО01-12-2010 06:13 AM
Re: locakble memory in dmesg
It is running on HP-UX 11.31.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 06:19 AM
тАО01-12-2010 06:19 AM
Re: locakble memory in dmesg
unlockable memory is RAM that is typically used by the kernel. operations that remain on the active queue and in memory are not released from unlockable memory
Lockable Memory
Pages kept in memory for the lifetime of a process by means of a system
call (such as mlock, plock, or shmctl) are termed lockable memory.
Locked memory cannot be paged and processes with locked memory
cannot be deactivated. Typically, locked memory holds frequently
accessed programs or data structures, such as critical sections of
application code. Keeping them memory-resident improves application
performance.
http://docs.hp.com/en/5965-4641/5965-4641.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 06:42 AM
тАО01-12-2010 06:42 AM
Re: locakble memory in dmesg
# kctune -v filecache_min
# kctune -v fs_meta_min
and also the memory utilization output from 'glance'?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 06:53 AM
тАО01-12-2010 06:53 AM
Re: locakble memory in dmesg
Tunable filecache_min
Description Minimum guaranteed physical memory used for caching file I/O data
Module fs_bufcache
Current Value 13073776640 [Default]
Value at Next Boot Default (automatic)
Value at Last Boot 13073776640
Default Value 13073776640 (automatic)
Can Change Automatic Tuning Enabled
hostname:/root #kctune -v fs_meta_min
Tunable fs_meta_min
Description Minimum guaranteed kernel memory used for metadata in the file cache
Module fs_bufcache
Current Value 2614755328 [Default]
Value at Next Boot Default (automatic)
Value at Last Boot 2614755328
Default Value 2614755328 (automatic)
Can Change Automatic Tuning Enabled
Mem util from Glance:
All Current, Avg. and High are 95%.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-12-2010 08:09 AM
тАО01-12-2010 08:09 AM
Re: locakble memory in dmesg
You could get more lockable by increasing the amount of available [reducing filecache_min from the default 5% to say 2% would give you another 6 or 7 Gb]. That's about all you could do. The system will not allow all free memory to be locked (since that would invite a free memory zero hang as soon as you need another page) and it is not adjustable in how much of free memory is considered lockable (aka the safety margin) in v3.