Our 3D CAD supplier models have been moved to 3Dfindit.com, the new visual search engine for 3D CAD, CAE & BIM models.
You can log in there with your existing account of this site.
The content remains free of charge.
Extract from
$CADENAS_SETUP ->
geomsearch.cfg
.
[Cache_Local_Search] maxOpenIndexCount=100 linIndexCacheSize=0 sampleLineListCacheSize=0 pivotDistListCacheSize=0 logFileName= [Cache_Server_Search] maxOpenIndexCount=100 linIndexCacheSize=150000 sampleLineListCacheSize=800000 pivotDistListCacheSize=50000 logFileName=
In the following you find an explanation for the individual caches:
GeoIndexCache: Prevents the index from being reopened for every new search.[20]The set value corresponds to the maximum number of open indexes.
Set the value to the number of catalogs to be searched through (in this case for example '100').
maxOpenIndexCount=100
(Cache is together for all Threads [usually corresponds to the number of processor cores] (compare $CADENAS_SETUP/partsol.cfg -> Block "SEARCHSERVER" -> key "THREADS")
Example: 80% of 1GB available RAM (indication in KB)
sampleLineListCacheSize=800000
linIndexCache: (not used for search of sketches)
Example: 15% of 1GB available RAM (indication in KB)
linIndexCacheSize=150000
pivotDistListCache: (not used for search of sketches)
Cache for Linear Index:[21]
(Cache is for all threads together [usually corresponds to the number of processor cores] (compare $CADENAS_SETUP/partsol.cfg -> Block "SEARCHSERVER" -> key "THREADS")
Example: 5% of 1GB available RAM (information in KB)
pivotDistListCacheSize=50000
You can optimize the settings in 2 steps:
Set the settings in the first step according to general experience:
Optimization of values according to the evaluation of the log file
In the
configuration file geomseach.cfg
you should
assign where the log file should be saved.
GeoIndexCache CacheHits 999 of 1000, 99% GeoIndexCache Files 99 of 100, 99% SampleLineListCache CacheHits 999 of 1000, 99% SampleLineListCache Memory 400000 of 800000, 50% LinIndexCache CacheHits 10617 of 10776, 98% LinIndexCache Memory 90000 of 100000, 90% PivotDistCache CacheHits 100 of 10000, 1% PivotDistCache Memory 9999 of 10000, 99%
For the GeoIndexCache you need not change anything. It is set to the number of catalogs to be searched through.
For the other three caches, you must pay attention to the following rules: (Here explained as an example for SampleLineListCache. The information LinIndexCache and PivotDistCache may be transferred.)
CacheHits is the measurement for the quality of the cache use. If this value is high, the settings are OK.
Memory gives information whether the value set in the configuration file is properly dimensioned. If you have 100% for CacheHits and 10% for Memory you can get just as many good CacheHits as with decidedly less allocations.
If the CacheHits are low (e.g. 10%) and the set cache is used completely (e.g. 100%), one should attempt to boost the hit rate by increasing the cache value.