Difference between revisions of "SET PSHARE"
Yvonnemilne (Talk | contribs) |
Helengeorge (Talk | contribs) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Purpose== | ==Purpose== | ||
Cause compiled programs and procedure libraries to load into shared memory | Cause compiled programs and procedure libraries to load into shared memory | ||
| Line 15: | Line 8: | ||
==See Also== | ==See Also== | ||
| − | COMPILE, DO, LINK, SET COMPILE, SET DEVELOPMENT | + | [[COMPILE]], [[DO]], [[LINK]], [[SET COMPILE]], [[SET DEVELOPMENT]] |
==Description== | ==Description== | ||
| − | The SET PSHARE ON command causes compiled ’.dbo’ programs and procedure libraries to load into shared memory . When PSHARE is set ON, the same physical memory allocated to an executed program referenced when the program is loaded again. Conserving physical memory in this way allows for more users per system. UNIX allocates shared memory segments physically above the ’heap’ (dynamic memory) storage area. Insufficient memory may result in the ’heap’ storage area as the shared memory stack increases in size. To adjust the dynamic memory size, the environment variable DB_HEAPSIZE may be set to a specified allocation block in units of 1K. DB_HEAPSIZE is defined in the file profile.db, and defaults to 32K. The shared memory facility must be built into the UNIX kernel in order for SET PSHARE ON to work. Please note that on UNIX system V, the kernel parameter SHMMAX (maximum shared memory size) should be set to a value capable of holding your largest program. The kernel parameter SHMALL (total shared memory system wide) may also need adjusting. If SET PSHARE is ON, and there is insufficient shared memory available, memory is allocated privately. | + | The SET PSHARE ON command causes compiled ’.dbo’ programs and procedure libraries to load into shared memory . When PSHARE is set ON, the same physical memory allocated to an executed program referenced when the program is loaded again. Conserving physical memory in this way allows for more users per system. UNIX allocates shared memory segments physically above the ’heap’ (dynamic memory) storage area. Insufficient memory may result in the ’heap’ storage area as the shared memory stack increases in size. To adjust the dynamic memory size, the environment variable DB_HEAPSIZE may be set to a specified allocation block in units of 1K. DB_HEAPSIZE is defined in the file profile.db, and defaults to 32K. |
| + | |||
| + | The shared memory facility must be built into the UNIX kernel in order for SET PSHARE ON to work. Please note that on UNIX system V, the kernel parameter SHMMAX (maximum shared memory size) should be set to a value capable of holding your largest program. The kernel parameter SHMALL (total shared memory system wide) may also need adjusting. If SET PSHARE is ON, and there is insufficient shared memory available, memory is allocated privately. | ||
==Example== | ==Example== | ||
| − | < | + | <code lang="recital"> |
set pshare on | set pshare on | ||
| − | do bigjob</ | + | do bigjob |
| + | </code> | ||
==Products== | ==Products== | ||
| − | Recital | + | Recital Server, Recital |
[[Category:Documentation]] | [[Category:Documentation]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
| − | [[Category:Set_Commands]] | + | [[Category:Set_Commands|PSHARE]] |
| + | [[Category:Environment]] | ||
| + | [[Category:Environment Set Commands]] | ||
| + | [[Category:Performance and Optimization]] | ||
| + | [[Category:Performance and Optimization Set Commands]] | ||
Latest revision as of 17:13, 23 November 2009
Purpose
Cause compiled programs and procedure libraries to load into shared memory
Syntax
SET PSHARE ON | OFF | (<expL>)
See Also
COMPILE, DO, LINK, SET COMPILE, SET DEVELOPMENT
Description
The SET PSHARE ON command causes compiled ’.dbo’ programs and procedure libraries to load into shared memory . When PSHARE is set ON, the same physical memory allocated to an executed program referenced when the program is loaded again. Conserving physical memory in this way allows for more users per system. UNIX allocates shared memory segments physically above the ’heap’ (dynamic memory) storage area. Insufficient memory may result in the ’heap’ storage area as the shared memory stack increases in size. To adjust the dynamic memory size, the environment variable DB_HEAPSIZE may be set to a specified allocation block in units of 1K. DB_HEAPSIZE is defined in the file profile.db, and defaults to 32K.
The shared memory facility must be built into the UNIX kernel in order for SET PSHARE ON to work. Please note that on UNIX system V, the kernel parameter SHMMAX (maximum shared memory size) should be set to a value capable of holding your largest program. The kernel parameter SHMALL (total shared memory system wide) may also need adjusting. If SET PSHARE is ON, and there is insufficient shared memory available, memory is allocated privately.
Example
set pshare on do bigjob
Products
Recital Server, Recital
