Notes.ini Entry


Name:
    FTG_Use_Sys_Memory

Syntax
    FTG_Use_Sys_Memory=0 / 1

Applies to:
    Servers

Add-on:

    First Release:
      6.5.3

    Obsolete since:

      Category:
        Full Text Index

      Default:
        None

      UI equivalent:
        None

      Description:
      This variable is new in 6.0.5 and 6.5.3

      This will instruct the full text engine to use direct malloc calls from the operating system for large allocations, instead of requesting memory through the Notes Memory Manager.

      SPR# MCAI5QDUSF - Fixed a problem where FTG_USE_SYS_MEMORY=1 full text performance tuning ini was not working in ND6. This ini should not be used unless recommended by IBM support and was a regression was introduced in 6.0.

      Steps available to optimize conditions (i.e. increase performance or reduce occurrence of 3301 --- or other GTR\search "out of memory" conditions:

      1. FTG_USE_SYS_MEMORY=1. Also see TN# 1090296 Database 'Lotus INTERNAL Knowledge Base', View 'Search View', Document 'How to Force the Full Text Engine to Use System Memory Instead of Notes Managed Memory'

      2. To use optimized settings (which helps prevent errcode = 3301) and improve search performance,: FTG_DISABLE_PAGING=1

      3. If that does not work (i.e. to eliminate errcode=3301) then use the following notes.ini FTG_SET_INITIAL_BUFLEN=7000 or 6000 or 5000, etc..

      note: The FTG_SET_INITIAL_BUFLEN can not be set less than 4096.

      NOTE: These "tools" are provided to the system admin in order to improve search results (i.e. reduce time on high "hit" result sets) and help prevent the "out of memory" conditions. These tools do not prevent all "out of memory" conditions from occurring --- because the resource consumption is directly related to the size of the database (i.e. number of documents), and to the type and characteristics of the query (i.e. number of unique keys), and to the system resources available at the time (i.e. hardware and activity dependent), etc..

      These tools help alleviate resource limits --- these tools do not eliminate all resource restrictions.