Best Practice for Cache Enviroment on HP-UX

Download Best Practice for Cache Enviroment on HP-UX

Post on 24-Mar-2015

76 views

Category:

Documents

6 download

TRANSCRIPT

Best Practices for Cach Environments on HP-UXVersion 2010.1 17 February 2010

InterSystems Corporation 1 Memorial Drive Cambridge MA 02142 www.intersystems.com

Best Practices for Cach Environments on HP-UX Cach Version 2010.1 17 February 2010 Copyright 2010 InterSystems Corporation All rights reserved. This book was assembled and formatted in Adobe Page Description Format (PDF) using tools and information from the following sources: Sun Microsystems, RenderX, Inc., Adobe Systems, and the World Wide Web Consortium at www.w3c.org.The primary document development tools were special-purpose XML-processing applications built by InterSystems using Cach and Java.

and Cach WEBLINK, Distributed Cache Protocol, M/SQL, M/NET, and M/PACT are registered trademarks of InterSystems Corporation.

,

,

and

InterSystems Jalapeo Technology, Enterprise Cache Protocol, ECP, and InterSystems Zen are trademarks of InterSystems Corporation. All other brand or product names used herein are trademarks or registered trademarks of their respective companies or organizations. This document contains trade secret and confidential information which is the property of InterSystems Corporation, One Memorial Drive, Cambridge, MA 02142, or its affiliates, and is furnished for the sole purpose of the operation and maintenance of the products of InterSystems Corporation. No part of this publication is to be used for any other purpose, and this publication is not to be reproduced, copied, disclosed, transmitted, stored in a retrieval system or translated into any human or computer language, in any form, by any means, in whole or in part, without the express prior written consent of InterSystems Corporation. The copying, use and disposition of this document and the software programs described herein is prohibited except to the limited extent set forth in the standard software license agreement(s) of InterSystems Corporation covering such programs and related documentation. InterSystems Corporation makes no representations and warranties concerning such software programs other than those set forth in such standard software license agreement(s). In addition, the liability of InterSystems Corporation for any losses or damages relating to or arising out of the use of such software programs is limited in the manner set forth in such standard software license agreement(s). THE FOREGOING IS A GENERAL SUMMARY OF THE RESTRICTIONS AND LIMITATIONS IMPOSED BY INTERSYSTEMS CORPORATION ON THE USE OF, AND LIABILITY ARISING FROM, ITS COMPUTER SOFTWARE. FOR COMPLETE INFORMATION REFERENCE SHOULD BE MADE TO THE STANDARD SOFTWARE LICENSE AGREEMENT(S) OF INTERSYSTEMS CORPORATION, COPIES OF WHICH WILL BE MADE AVAILABLE UPON REQUEST. InterSystems Corporation disclaims responsibility for errors which may appear in this document, and it reserves the right, in its sole discretion and without notice, to make substitutions and modifications in the products and practices described in this document. For Support questions about any InterSystems products, contact: InterSystems Worldwide Customer Support Tel: +1 617 621-0700 Fax: +1 617 374-9391 Email: support@InterSystems.com

Table of ContentsBest Practices for Cach Environments on HP-UX............................................................................. 1 1 Processor ....................................................................................................................................... 1 2 Software and Patches ..................................................................................................................... 1 2.1 Location of Patches and Service PAKs .............................................................................. 1 3 Storage ........................................................................................................................................... 2 4 LVM/VxVM .................................................................................................................................. 2 5 File systems (VxFS) ...................................................................................................................... 2 6 Network Parameters ...................................................................................................................... 3 7 Key Kernel Tunable Parameters .................................................................................................... 3

List of Tables Table 1: Key Kernel Tunable Parameters ......................................................................................... 3

Best Practices for Cach Environments on HP-UX iii

Best Practices for Cach Environments on HP-UXThis article provides general guidelines on how to configure HP-UX 11i v2 and 11i v3 systems for use in Cach-based environments. It assumes that you are using Cach version 2007.1 or later. Unless otherwise noted, the recommendations in this article are applicable to all systems used as a Cach/Ensemble database server. These recommendations are based on the configurations developed and tested jointly by InterSystems, Inc. and Hewlett-Packard Company.

1 ProcessorFollowing are the recommended processor requirements: Configure memory for maximum interleaving. On most systems, all DIMM slots should be filled with the same size DIMMs. Consult the documentation for your particular platform for precise rules. On multi-cell systems, configure with no cell local memory. Configure swap space equal to at least 1.5*physical memory. Most current firmware.

2 Software and PatchesFollowing are the minimum software requirements: HP-UX 11.23 or 11.31 MCOE on 11i v2 All current supplementary patches (use SWA to check) SecurePath, PowerPath, or native 11i v3 fiber channel multipathing HP-UX Software Assistant (SWA) Glance Disable kcmond (kcalarm -m off)

2.1 Location of Patches and Service PAKsAll Service PAKs and patches are available for download from the IT Resource Center (ITRC) at the following URL: http://www2.itrc.hp.com/service/home/hpMaint.do.

Best Practices for Cach Environments on HP-UX1

Storage

3 StorageLUNs should be configured as follows: Transaction journal LUN optimized for fast processing of continuous small (~1-4 KB block size) single-stream sequential writes - high IOPS (RAID1+0, no parity-based RAID) WIJ LUN optimized for fast processing of large (256-KB block size), single-stream sequential write bursts (RAID1+0, no parity-based RAID) Database LUN(s) optimized for random 8-KB reads/writes (RAID1+0 strongly preferred) Installation and other LUN(s) as required SecurePath/PowerPath/etc. should be configured to load balance using the SST (Shortest Service Time) algorithm, if available, or with preferred path.

4 LVM/VxVMLVM/VxVM striping should not be used. If a filesystem requires the use of multiple LUNs, use concatenation or, if striping is required, use only extent-based striping. If possible, avoid LVM/VxVM mirroring.

5 File systems (VxFS)At least 3 separate filesystems are required: WIJ (write image journal) Transaction journal (critical for ECP applications) Databases Installation and others as required

Software installation directories may be included in the WIJ filesystem. All filesystems should be created with: mkfs -F vxfs -o bsize=8192,largefiles [special]. Create /etc/vx/tunefstab, including the lines:[block-device for wij] discovered_direct_iosz=512K,\ write_pref_io=256K,max_diskq=1G,max_buf_data_size=64K [block-device for DBfs1] max_diskq=16M [block-device for DBfs2] max_diskq=16M . . .

The file must contain the /dev/... special device files used to mount the filesystems, not the paths to the filesystems themselves. Mount all filesystems with the mount options "delaylog,largefiles". On VxFSV5, also include the mount option "noqio".

2Best Practices for Cach Environments on HP-UX

Network Parameters

Do NOT use DirectIO (mount options "mincache=direct,convosync=direct") for the WIJ. DirectIO (or Concurrent IO on VxFSV5) may be used for database file systems if desired, but will degrade write performance, which may cause a problem with heavy write loads (e.g. during batch updates).

6 Network ParametersThe following parameters should be inserted in /etc/rc.config.d/nddconf to support gigabit ethernet:TRANSPORT_NAME[0]=tcp NDD_NAME[0]=tcp_recv_hiwater_def NDD_VALUE[0]=262144 TRANSPORT_NAME[1]=tcp NDD_NAME[1]=tcp_xmit_hiwater_def NDD_VALUE[1]=262144 TRANSPORT_NAME[0]=tcp NDD_NAME[2]=tcp_recv_hiwater_lfp NDD_VALUE[2]=262144 TRANSPORT_NAME[2]=tcp NDD_NAME[3]=tcp_xmit_hiwater_lfp NDD_VALUE[3]=262144 TRANSPORT_NAME[4]=sockets NDDNAME[4]=socket_udp_rcvbuf_default NDD_VALUE[4]=262144 TRANSPORT_NAME[5]=sockets NDD_NAME[5]=socket_udp_sndbuf_default NDD_VALUE[5]=262144

7 Key Kernel Tunable ParametersHP recommends that only parameters that are different from the OS default value are included in the /stand/system file. HP further recommends that changes to the /stand/system file are made only using the kctune command and that parameters not explicitly mentioned here be explicitly set to default values, as follows: Revert to default: kctune [parameter]= Set parameter to expression: kctune [parameter]="[expression]" When the version of the release to which a parameter applies is not explicitly mentioned, the recommendation is valid for all versions of HP-UX 11i v2 and 11i v3.

Table 1: Key Kernel Tunable ParametersParameter dbc_max_pct dbc_min_pct1

Value 12GB 2

Notes Percentage of physical memory Same as dbc_max_pct Flush behind policy Requires hi-res timer patches Enable hyperthreading

1

fcache_fb_policy

1 1 1

hires_timeout_enable lcpu_attr

Best Practices for Cach Environments on HP-UX3

Key Kernel Tunable Parameters

Parameter nkthread nproc

Value 30100 30000

Notes Threads allowed to run simultaneously (nproc+100) 30000=maximum for 11i v2 60000=maximum for 11i v3

maxuprc nclist3

28000 8292 5600066 600 6003

Maximum procs/user Number of cblocks for pty and tty min 8292 System-wide open files Maximum streams-based ptys Maximum telnet device files Enables translation of O_SYNC to O_DSYNC Maximum PID number

nfile

nstrpty nstrtel o_sync_is_o_dsync process_id_max2 3

1 31000

scsi_max_qdepth

Set appropriate value for storage subsystem: For EVA,

Recommended

View more >