Merging parameters - Alfresco Search Services - 2.0 - 2.0 - Ready - Alfresco - external - Alfresco/Alfresco-Search-Services/2.0/Alfresco-Search-Services/Configure/Performance-Recommendations/Merging-parameters - 2025-04-04

Alfresco Search Services

Platform
Alfresco
Product
Alfresco Search Services
Release
2.0
License

From version 2.0.2 following parameters has been exposed to be used from solrcore.properties file.

Property Description
merge.policy.maxMergedSegmentMB This number shoud be increased for large deployments. For instance, when using a 40+ million indexed nodes with content on a SOLR Shard. You may use 10240 instead of 5120. The default is 5120.
merge.policy.maxMergeAtOnce The numbers should be decreased in order to reduce the number of segments. This also improves searching performance when using 40+ million indexed nodes with content on a SOLR Shard. You may use 5 instead of 10. The default value is 10, Note: The value used must be the same as for merge.policy.segmentsPerTier.
merge.policy.segmentsPerTier The numbers should be decreased in order to reduce the number of segments. This also improves searching performance when using 40+ million indexed nodes with content on a SOLR Shard. You may use 5 instead of 10. The default value is 10, Note: The value used must be the same as for merge.policy.maxMergeAtOnce.
merger.maxMergeCount Increment this number for large deployments, so more merge operations can be executed simultaneously. The default value is 6.
merger.maxThreadCount This number should always be lower than the amount of dedicated CPUs and also lower than mergermaxMergeCount. Increment this number for large deployments in order to use all your available CPU threads. The default value is 3.
Note: Changing any of these values requires a full re-index of your SOLR Core in order to get the performance benefits.