Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

HP-UX Kernel configuration for Dassault Systemes products

» 

Workstations 

» Products
» Workstations
» Mobile Wokstations
» Leadership graphics
» Performance Tuning Framework
» Remote Graphics
» HP Workstations with Linux
» Customer stories
» White Papers
» Discontinued products
» Special offers
» Easy financing
» Find a reseller
» Other ways to buy
» Support & Drivers
» Solutions
» Services
» News & Events
» Request printed catalog
» Sign up / update email
Content starts here

Most of the parameters of the HP-UX systems is managed through the kernel. Ensure your system is properly configured for all Dassault Systemes products by reviewing the following information. This information applies to both HP-UX 10.20 and 11.x.

To know the current settings of your kernel, execute as root the 'sysdef' command which returns the name of the parameter, its current value, its range value and its unit. You can also use the 'kmtune' command only available on HP-UX 11.

Use SAM: Kernel Configuration > Configurable Parameters to update the kernel values.

  • minor file system performance opt
    • create_fastlinks = 1

  • Setting to insure process can allocate large data
    • maxdsiz =
      HP-UX 10.20 2063835136 (decimal)
      UX 11x for 32 bits apps using +q3p: 0xC0000000

  • Setting to allow large applications to use deep call stacks
    • maxssiz= 1024*1024*80 (corresponds to 80MB)

  • Setting to permit large text space applications to load
    • maxtsiz= 1024*1024*1024 (corresponds to 1GB)

  • Setting to permit apps to open large number of files
    • nfile = 4000

  • Ninode sizes the in-core inode table, also called the inode cache. For performance, the most recently accessed inodes are kept in memory
    • ninode = 4000

  • Strong files system performance opt. If your app does repeated access (random especially) to lots of file system data then you want this set to cover the amount of file system you use. The trade off is that physical memory is more or less exclusively allocated here, away from application in-memory data structures.
    • Choose dynamic behavior by setting dbc_max_pct and dbc_min_pct to the desired percentages of physical memory. Dynamic behavior is not always the best performing.

      Choose fixed size with: dbc_max_pct = dbc_min_pct = x% where you have calculated the % of physical memory and choosen y MB of space for buffer cache

  • disk space for greater total virtual memory area. Only physical memory provides fast application performance so this swap space is typically for large process(s) where only one (or part of one process) is actively using memory up to your physical memory size at one time.
    • Typical setting is 2-4GB. Choose “device swap” space at HP-UX installation time or use SAM to create additional “device swap” after installation.

Contact me >> Contact me

» HP in MCAD
» HP for Dassault Systèmes Users
» Dassault Certification Status
» HP and Dassault Systemes brochure (PDF, 4MB)

Choose your solution

» HP Personal Workstation
» HP Mobile Workstation
» HP-UX Workstation
» HP Remote Graphics Software
» HP Performance Tuning Framework
» HP Large Format Printers

Technical information

» HP-DS PLM Competence Center
» Iterate More, Innovate Faster: The Benefits of Quad-Core (.pdf, 421K)

Related links

» Dassault Systemes Solutions
» HP and Dassault Systemes brochure (.pdf, 4MB)
» HP Partner Program for software developers

Notes

  • You may get some messages related to the shared memory usage, like 'quad4map_32bit rmap ovflo ...'. This message is caused by fragmentation in the 4th quadrant where shared objects are located. Try to increase the shmmni parameter to an higher value (default is 200) and reboot your system.
    'shmmni' specifies the maximum number of shared memory segments allowed to exist simultaneously, system-wide. Value cannot exceed 1024.
  • If you use a server based installation and then execute CATIA on clients, the default behavior of the application is to page TEXT (code) back to the server. Setting the page_text_to_local kernel parameter to 1 will solve this behavior and then reduce the network traffic. It does not affect shared library text (code).
Printable version
Privacy statement Using this site means you accept its terms
© 2008 Hewlett-Packard Development Company, L.P.