tuxedo管理(6)

BEA Tuxedo管理手册

Servers with Reply Queues) - (No. Servers in MSSQ Set) + (No. MSSQ Sets) + 7) to determine the appropriate value

? MSGMAP: Number of entries in control map used to manage message segments (Not defined

in NT). Set to 2 * MSGMNI ? MSGMAX: Maximum message size in bytes. Set to the largest message size or 75% of the

queue size (whichever is bigger) ? MSGMNB: This is the queue size itself (64K, 128K, etc.)

? MSGSSZ: Size of a segment in bytes (Not defined in NT). The value of MSGSSZ should be

such that a multiple of MSGSSZ is equal to the size (including the BEA TUXEDO System header) of the most commonly sent message. Usually set to 16, 32, or 64. ? MSGTQL: Total Number of In-Flight messages in the system at once

? MSGSEG: Number of message segments in the system (Not defined in NT). You need to find

out the queue space of your machine and then the following formula applies: MSGSEG * MSGSSZ = Machine Queue Space Size (note it will swap)

Semaphores Parameters

? SEMMNS: Maximum number of semaphores in the system. The minimum requirement for

SEMMNS is MAXACCESSERS - MAXWSCLIENTS + 13 (local clients and all servers) ? SEMMNI: Maximum number of active semaphore sets. For small apps,(100 to 500

servers),10 sets are usually sufficient. For large apps, (>500 servers) 32-64 sets are usually sufficient (do a tmloadcf -c to see which is the best) ? SEMMSL: Maximum number of semaphores per semaphore sets (Not defined in NT). Use

the formula: SEMMNS = SEMMNI * SEMMSL ? SEMMAP: Size of the control map used to control semaphore sets (Not defined in NT). Set

to SEMMNI ? SEMMNU: Number of undo structures in the system. Set to SEMMNS

? SEMUME: Maximum number of undo entries per undo structure (Not defined in NT). Set

to SEMMNS

Shared Memory Parameters

? SHMMAX: Maximum shared memory segment size in bytes. Bulletin Board Size (must be

greater than 1,400,000). Largest BB today is approx. 5 MB (this parameter is normally set much higher for the database, so use their rules) ? SHMSEG: Maximum number of segments one process can attach to (for a busy application

you need to set this from 32-64) ? SHMMNI: Maximum number of shared memory identifiers in the system. Normally the

default of 100 is acceptable (unless more than 100 entities plan on allocating shared memory) ? SHMMIN: Minimum shared memory segment size in bytes. MUST be set to 1.

第 26 页 共 27 页

BEA Tuxedo管理手册

Other Tunables

? ULIMIT: Maximum file size. ULIMIT needs to be large enough so that you can install BEA

TUXEDO and build servers. 4 megabytes recommended.

? MAXUP: Maximum number of processes per non-super user. The BEA TUXEDO

system processes--servers and administrative processes—run with the UID specified in the application's UBBCONFIG file. MAXUP needs to be large enough to allow all of these processes to run.

? NOFILES: Maximum number of open files per process. A BEA TUXEDO server requires a

minimum of four file descriptors.

? NPROC: Maximum number of processes (systemwide).

? NREGION: Number of region table entries to allocate. Most processes have three regions:

text, data, and stack. Additional regions are needed for each shared memory segment and shared library (text and data) attached. However, the region table entry for the text of a ``shared text'' program is shared by all processes executing that program. Each shared memory segment attached to one or more processes uses another region table entry.

? NUMTIM: Maximum number of STREAMS modules that can be pushed by the Transport

Layer Interface (TLI). A typical default value is 16; you should have it set to at least 256.

? NUMTRW: The number of TLI read/write structures to allocate in kernel data space. A

typical default value is 16; you should have it set to at least 256.

第 27 页 共 27 页

百度搜索“77cn”或“免费范文网”即可找到本站免费阅读全部范文。收藏本站方便下次阅读，免费范文网，提供经典小说综合文库tuxedo管理(6)在线全文阅读。