Changes

If main memory runs out while creating a value index, the currently generated index structures will be partially written to disk and eventually merged. If the used memory heuristics fails for some reason (i.e., because multiple index operations run at the same time), fixed index split sizes may be chosen via the <code>[[Options#INDEXSPLITSIZE|INDEXSPLITSIZE]] </code> and <code>[[Options#FTINDEXSPLITSIZE|FTINDEXSPLITSIZE]] </code> options.

If [[Options#DEBUG|DEBUGdebugging]] is set to trueenabled, and if a new database is created from the command line, the number of index operations will be output to standard output; this might help you to choose a proper split size. The following example shows how the output can look for a document with 111 MB and 128 MB of available main memory:

The info string {{Code|3 splits}} indicates that three partial full-text index structures were written to disk, and the string {{Code|12089347 operations}} tells that the index construction consisted of approximately 12 mio index operations. If we set <code>[[Options#FTINDEXSPLITSIZE|FTINDEXSPLITSIZE]] </code> to the fixed value {{Code|4000000}} (12 mio divided by three), or a smaller value, we should be able to build the index and circumvent the memory heuristics.