Fulltext search server performance tuning

When encountering performance issues with Fulltext search, you observe that processes Yoda, Yoda-scan or Mundi are utilizing the server resources. There are several settings which can be adjusted.

All the configuration files listed below are in the Yoda folder in your Icewarp directory. Please note that these settings matter only if these services run locally (there’s also an option to run Fulltext search on a dedicated VM).

Values shown below in variables are default ones, so you can lower the values if they affect the server’s performance – please note that zero (0) means unlimited.

YODA.XML

• <max_cpus>4</max_cpus> - maximum number of occupied cores of CPU

YODA-SCAN.XML

• <max_cpus>4</max_cpus> - maximum number of occupied cores of CPU
• <max_jobs>4</max_jobs> - number of parallel processes, affects RAM usage
• <max_indexed_items_per_sec>0</max_indexed_items_per_sec> - affects CPU usage
• <listed_files_batch_size>25</listed_files_batch_size> - affects storage usage

MUNDI.XML

• <max_cpus>4</max_cpus> - maximum number of occupied cores of CPU
• <max_jobs>4</max_jobs> - number of parallel processes, affects RAM usage
• <max_ooconverters>2</max_ooconverters> - affects RAM usage
• <max_ocrs>4</max_ocrs> - affects CPU & RAM usage

You can adjust the network bandwidth according to your network utilization.