Installgen
Features and Benefits
Installgen
Demo Available for download...
Bookmark This Page
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
* file: /etc/system (renamed from 38_sol_920_etc_system_1.txt
* Features: This is the customized version of the /etc/system file
* which contains the kernel tuning parameters required for
* the Oracle database installation. These parameters are
* customized based upon the SGA and available memory.
*
* Script Sequence#: 38
* Used By: Solaris during OS startup
* Copyright 2002 by .com Solutions Inc.
*
* ---------------------- Revision History ---------------
* Date By Changes
* 09-28-2001 dsimpson Initial Release
* 05-30-2002 dsimpson added @ where needed
* This output file was created by Installgen version 1.38 on Sun Nov 10 14:20:50 2002. By .com Solutions Inc. www.dotcomsolutionsinc.net
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
*
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
* shmmax of 0xffffffffffffffff means allow use of all memory available for Oracle
* SEMMNS 4096 (for 1000 Oracle processes), 40960 (for 10000 Oracle processes)
* SEMMSL 2048 (for 1000 Oracle processes), 20480 (for 10000 Oracle processes)
set shmsys:shminfo_shmmax=0xffffffffffffffff
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=256
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmns=4096
set semsys:seminfo_semmni=4096
set semsys:seminfo_semmsl=2048
set semsys:seminfo_semopm=100
set semsys:seminfo_semmap=256
* kernel_caged_enable - used for Dynamic Reconfiguration - disabled when using ISM
* ISM allows pages to be locked in memory for Oracle
*set kernel_cage_enable=1
* Also make sure use_ism=false is not located in init.ora
* ****** Additional Sun recommended performance tuning changes ******
* UFS write throttling High-Water mark:
* The default for this is quite low and needs to be increased if the system
* has high-speed IO devices underlying the UFS filesystem.
* The counter ufs_throttles will accumulate each time the system throttles
* on this condition. So check this and if ufs_throttles is a large value
* you need to increase ufs_HW.
* INTERNAL References to more info
* ref. http://devnull.eng.sun.com/Solaris/Solaris_FStune.html
* http://www.corp/prodmktg/pme/newstop/setimes/1995/June30,1995/solaris_tune
* Recommendation, have at least 1-track (~64k * # disks in stripe), and
* at least maxphys.
* DEFAULT: 393216
* UNITS: Bytes of outstanding IO on a per file basis
* set ufs:ufs_HW=4194304
* fsflush tuning
*
* The default for these are 30 seconds for autoup, and 5 seconds for fsflushr,
* This will make the fsflush process way too hot on a big memory machine.
* Cool it out by reducing the cycle time, autoup and/or increasing the
* run interval: tune_t_fsflushr
* The system may exhibit periodic freezes when fsflush runs. To
* troubleshoot this performance problem, try temporarily setting
* dopageflush to 0 to turn off fsflush alltogether, and/or set doiflush=0 to
* turn off inode flushing only. (Do this with adb for just a few minutes!!!)
*
* autoup
* DEFAULT: 30
* UNITS: seconds
* REBOOT REQUIRED: YES
set autoup=900
*
* tune_t_fsflushr
* DEFAULT: 5
* UNITS: seconds
* REBOOT REQUIRED: NO
set tune_t_fsflushr=1
* maxphys
* For 2.5.1 and higher kernels, we have the capability to do large IOs to
* and through the lowest layers. This is important for DSS. Also "plaid"
* striping where veritas is used to stripe RAID-5 Luns with the recommended
* 512k or 1024k Stripe interlace. Be sure to check your settings for
* volume manager software to take complete control of the blocksize out to
* the IO device. (See vxio:vol_maxio and or sd_maxphys sections.)
* WARNING: this has a side-effect on maxcontig for sd devices.
* See maxcontig in "NOTES" section at the end of this document.
* DEFAULT: 131072
* UNITS: bytes
* REBOOT REQUIRED: YES
* set maxphys=1048576
* Soft Affinity
* rechoose_interval
* UNITS: Ticks
* REBOOT REQUIRED: YES
* This variable instructs the kernel on which cpu to select to run a thread
* if a choice needs to be made. So if a process hasn't run in rechoose_interval
* ticks it will be moved to another CPU. Otherwise it will continue to wait
* on the CPU it has been running on.
*
* A higher value of rechoose_interval "firms-up" the soft affinity. The down
* side is that you can end up with sluggish spreading out of processes on an
* application where a single processes forks a lots of children if this value
* is too high.
* A problem where threads migrate unnecessarily (Bugid 4103680) has been fixed
* in 2.7.
*
* DEFAULT: 3
* RECOMMENDATION: The answer is somewhere in between 3 and 300.
* REBOOT REQUIRED: YES
* set rechoose_interval=30
* bufhwm -- Buffer High Water Mark
* Limits the amount of memory devoted to buffer headers cache. The
* default is too high for large memory machines, set smaller and you can
* recover nearly all that space. Watch for values too small with sar -b.
* DEFAULT: 2% of all physical memory.
* UNITS: KBytes
* REBOOT REQUIRED: YES
* set bufhwm=8000
* segspt_minfree Solaris 2.6 and above
* Leaves at least this much memory free when allocating ISM shared memory
* for parts of the kernel that haven't paged in yet. This is because ISM
* shared memory implies non-pagable memory, and thus the kernel assumes it
* will never get to use this memory. The default is too high for large memory
* machines and would make more sense to be limited to a few dozen MB.
* Becomes CRITICAL if you are trying to allocate all memory for
* the database shared memory pool, (Informix XPS for example)
* DEFAULT: 5% of available real memory.
* UNITS: Pages
* REBOOT REQUIRED: YES
* adb r/w: E/Z
* set segspt_minfree=12000
* rlim_fd_max
* Increases the maximum number of open file descriptors, no guarantees for
* really large values, but small increases should be OK.
* DEFAULT 1024
* UNITS: number of files, 32-bit
* REBOOT REQUIRED: YES
set rlim_fd_max=2048
* ndd Tuning ??? setting to use for Gbit Ethernet???
* ndd tuning of the devices /dev/tcp /dev/ge fall in the category of kernel
* tuning. tcp_xmit_hiwat is the most common subject of tuning. The default
* under most kernels is small, and therefore you can find places that
* recommend running around 256k if you have interfaces faster than 100BaseT.
* The default was 256k in Solaris 2.6.
