7.3.3. Configure caching

Here, there is only one cache anymore, where the size has to be adjusted. The storage is stated in KB here.

[CACHE_GEODB]
TableCacheSize=5000000

When starting the AppServer parts of the GeoDb are loaded into the memory. This can be controlled by rules. Per default there are 2 rules defined here; one for the own part catalogs (native) and one for other catalogs (default). You can add any number of rules here.

[settings]
GeoDbPreloaderRules=Default,Native

There is a block for each rule at geomsearch.cfg. First, you specify the catalogs to which the rule should apply. Here is an example of a typical configuration:

[GeoDbPreloaderRule_Default]
Catalogs=*

[GeoDbPreloaderRule_Native]
Catalogs= cat/mycatalog1,cat/mycatalog2

If * is stated, the rule applies for all catalogs, for which no other rule has been stated explicitly. Of course, this should only be used in one rule. Then in each block the use cases can be stated for which data should be preloaded. The standard configuration for not-native catalogs is:

[GeoDbPreloaderRule_Default]
GeoSearchTemplates=SystemTemplate1,SystemTemplate4,SystemTemplate7
GlobalAttributes=1
FeatureAttributes=0
Partial=0
RawPart=0
Color=1

Here, search templates for the size-depending and not size-depending standard search and the sketch search are preloaded, for topo searches for global parameters (size, symmetry, etc) and for the color search.

[GeoDbPreloaderRule_Native]
GeoSearchTemplates=SystemTemplate1,SystemTemplate4,SystemTemplate7
GlobalAttributes=1
FeatureAttributes=1
Partial=1
RawPart=1
Color=1

For own part catalogs the topo search for features (cone, holes, hole patterns, etc.) is activated in addition by default.

Also partial and raw part search are turned on by default. If no indices had been created for this, the setting has no effect.

If you know the use cases for a customer, you can adjust the values accordingly.

If the data for use cases is not pre-loaded, the search will work anyhow. It only may be the case that the first access on related data lasts a bit.

In many environments, it will be sufficient to list the own parts catalogs in the GeoDbPreloaderRule_Native block.