Parameter:
FTG_MB_PER_THREADShort description: Maximum working memory per full-text indexer thread for Tika attachment conversion; default 1 MB.
Profile
Parameter | FTG_MB_PER_THREAD |
Category | Performance / Memory |
Component | Server |
Available since | 9.0.1 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | Integer in MB; default 1 |
Description
FTG_MB_PER_THREAD defines how much working memory a single thread of the Domino full-text indexer may use at most for attachment conversion (Tika). The parameter works together with FTG_MAX_NUM_THREADS and FTG_MAX_MEM_POOL: if FTG_MAX_MEM_POOL is not explicitly set, Domino computes the global memory pool from FTG_MB_PER_THREAD × FTG_MAX_NUM_THREADS. Without further configuration, the default of 1 MB per thread applies.Raising the value is worthwhile especially on servers with extensive Office or PDF attachments whose Tika conversion has too little memory at the default value. Higher values prevent out-of-memory aborts when indexing large files, but increase the overall FT memory footprint accordingly; in practice, values between 4 and 16 MB are common.
Example configuration
FTG_MB_PER_THREAD=8
Notes & pitfalls
- Affects all FT index tasks (Update, Updall, FTUPDATE, Domain Indexer); part of the FTG memory family together with
FTG_MAX_MEM_POOL,FTG_CHECK_THREAD_MAX_MEM, andFTG_USE_SYS_MEMORY.
- If
FTG_MAX_MEM_POOLis set explicitly, that value takes precedence over the calculationFTG_MB_PER_THREAD × FTG_MAX_NUM_THREADS.
- Values that are too low lead to Tika aborts in the console log for large attachments; with
FTG_CHECK_THREAD_MAX_MEM=1the memory behavior can be verified.
- Changes only take effect after a restart of the FT tasks or the server;
set config FTG_MB_PER_THREAD=…alone is not sufficient.