1.7.5.8.  geomsearch.cfg
1.7.5.8.10. Cache search results in working memory
Prev  Next
1.7.5.8.10. Cache search results in working memory
1.7.5.8.10.1. Caching for versions up to 9.07
1.7.5.8.10.1.1. Description of different caches
1.7.5.8.10.1.2. Log file evaluation - Find best settings
1.7.5.8.10.2. Caching / geometric search index as of V9.08
1.7.5.8.10.2.1. Structure of indices
1.7.5.8.10.2.2. geomsearch.cfg -> Block [settings] - Common settings
1.7.5.8.10.2.3. Creation of Geo and Topo indices
1.7.5.8.10.2.4. Changes at the actual search
1.7.5.8.10.2.5. Caching settings
1.7.5.8.10.2.6. Log file evaluation - Find best settings
1.7.5.8.10.2.7. Access on Topology values via VBS

Most time spent during a search is used for the reading of data from a hard drive. Therefore the search is faster if results can be cached in a working memory.

Caching is especially recommended for use with the search server.

[Note]Note

When restarting the PARTdataManager or the search server the cache is lost. Therefore, an effective caching is only possible within a search server, since this is usually only restarted in extreme cases.

[Note]Note

Beside the here described caching there is still another between the index files and the search server.

Important information on this is found under Section 1.3.9.9.3.6, “ Caching index files of $CADENAS_DATA on PARTapplicationServer ”.

In the configuration file geomsearch.cfg there are different sections for performing the caching:

  • Caching for versions up to 9.07

    [Cache_Local_Search]
[Cache_Server_Search]

    [Note]Note

    The settings possibly remain relevant also for versions as of 9.08, because these can alternatively use the "old" search index.

  • Caching for versions as of 9.08

    [CACHEV2_GEO_SEARCH_32]
[CACHEV2_GEO_SEARCH_64]

In the following the sections are explained separately:

Prev Up Next
1.7.5.8.9. Dependency of extension values from orientation  Home 1.7.5.8.10.1. Caching for versions up to 9.07