Product Area: Server  Technical Area: Search Platform: Cross Platform
SPR# JSTN8C52GM - Limit Full Text Index Search GTR query memory consumption in order to lessen or eliminate server instability. There are several new notes.ini variables that control Full Text Search memory usage:
FTG_CHECK_THREAD_MAX_MEM - turns on (=1) or off (=0) the per-thread memory check mechanism. Default is 0.
FTG_MAX_MEM_POOL=<concurrent threads> - controls the allocation of the per-thread memory check mechanism. Set this to the maximum number or concurrent threads that can perform a full-text search. Default is 512.
FTG_MAX_MB_PER_THREAD=<megabytes> - sets the maximum megabytes allowed for a single thread's full text search to consume. Default is 100.
FTG_MB_PER_THREAD=<megabytes> - sets the maximum megabytes per-thread allowed for all threads concurrently performing a full-text search. This number is only used in conjunction with FTG_MAX_MEM_POOL, where FTG_MAX_MEM_POOL*FTG_MB_PER_THREAD is the global limit of combined full-text memory usage in the server. Default is 1, so the default maximum global limit is 512MB.
FTG_USE_SYS_MEMORY - turns on (=1) or off (=0) for 64-bit systems with ample memory, this setting avoids the use of Domino memory pools and allocates directly from RAM. With additional RAM there is no reason that any full text query will fail due to lack of memory. Default is 0.
APAR: LO16886
What is an APAR?
Last Modified on 11/12/2015 |  |
|
|
|
|
|