- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- Re: Partition configuration
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
тАО05-26-2006 01:44 PM
тАО05-26-2006 01:44 PM
What are the situations that you would want or not want to have memory interleaving? What are the benifits/drawbacks of putting a value in the field. What would be a "good"/"bad" value to use.
It appears that all machines delivered by HP have 0 on all cell boards in the single partition set to 0. Is this a hint to not use the clm_value?
If a value should be used how does one specify it in the genesis partition?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2006 01:27 AM
тАО05-27-2006 01:27 AM
Re: Partition configuration
In superdomes don't mix DIMM sizes. Its critical for all DIMMS to have identical sizes and I believe 512MB is the Superdome size. But might be different for other servers. So what server model.
Review this document for a better discussion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2006 03:39 AM
тАО05-27-2006 03:39 AM
Re: Partition configuration
See attached parcreate description.
Map out your local and shared / interleaving memory.
'0' (zero) defaults to 100% ov memory used for sharing and interleaving.
"...If no clm_value is specified, maximum interleaved memory (no CLM) is assumed for cells...".
Since 0 (zero) is the default, I'd accept it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-27-2006 03:52 AM
тАО05-27-2006 03:52 AM
Re: Partition configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-28-2006 09:02 PM
тАО05-28-2006 09:02 PM
Solutionif a CPU want to access memory, it is faster to get the memory from the same cell as the CPU (local memory) as from other cells (memory traffic goes through the backplane).
This means that you have different latencies when accessing memory dependent of where the memory is located.
Interleaving has the advantage that this latency is constant, because each cache line is distributed on all cells.
HPUX 11.23 provides the funcionality that the programmer can better control the memory usage. If the application supports it, you can have some performance advantage if your process is only using memory from the same cell. Of course, this should only be done, if 1.) all threads that use this memory are running on the same cell and 2.) the memory on that cell is sufficient. If the process uses additional memory from other cells, this would slow down the application.
HPUX 11.23 by default tries to use local memory first if appropiate and available.
See HPUX 11.23 Release Notes for more details on this.
http://docs.hp.com/en/5990-6737/ch11s02.html?jumpid=reg_R1002_USEN
Attention: Do not use Cell local Memory on a HPUX 11.11 system. The memory would be invisible to the Operating System.
best regards
Stefan