Open topic with navigation
To tune indexing performance, you can adjust certain limits on the DIH and its child servers.
Specify how many times the DIH attempts to send an index action to a child IDOL server before it assumes that the connection has failed.
Limit the number of indexing threads that DIH can employ.
Set the value in the
Threads configuration parameter (in the [
Server] section of the DIH configuration file). The default value is 10 threads. HPE recommends that you use (1 x Num. CPUs) + 1 spare thread.
Limit the size of an indexing request string, which limits the amount of data that you can index in a single request.
MaxInputString configuration parameter (in the [
Server] section of the DIH configuration file) to the value that you want. The default value is
64000. A value of
-1 means that there is no limit.
Specify that DIH must have a certain amount of available disk space for indexing to proceed.
MinFreeSpaceMB configuration parameter (in the
[Server] section of the DIH configuration file) to the minimum amount of disk space that DIH must have. By default, DIH must have 20 MB of disk space.
Specify that a certain number of child IDOL servers must be running for indexing to proceed.
Stop the DIH from turning
DREADD actions into
PreserveDREADD configuration parameter (in the
[Server] section of the DIH configuration file) to
True. This option reduces network load by sending only the path to the IDX file to child servers, rather than streaming all the contents of the IDX file. You can use this parameter only in simple mirror or non-mirror mode. You must ensure that all child servers can access the file system containing the IDX file with the same file path.
Use weighted indexing to alter the ratio in which documents distribute to different servers in standard distributed mode.
A server with weight
2 receives twice as many documents as a server with weight
1 and so on. You can set a weight of
0 to add no documents to a server.
Use round-robin indexing to maximize indexing performance without compromising the IDOL Server pool availability. See Round Robin Indexing.
Use reference-based indexing to distribute the indexing load evenly between IDOL Servers. See Reference-Based Indexing.
Use field-based indexing to distribute the indexing load evenly between IDOL Servers. See Field-Based Indexing.
Use date-based indexing to distribute the indexing load between IDOL servers. See Date-Based Indexing.