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{{Mark|FTINDEXSPLITSIZE]]</code> optionsUpdated with Version 8.4:}}

If [[Options#main memory runs out while creating a value index, the current index structures will be partially written to disk and eventually merged. If the memory heuristics fail for some reason (i.e., because multiple index operations run at the same time, or because the applied JVM does not support explicit garbage collections), a fixed index split sizes may be chosen via the {{Option|SPLITSIZE}} option. If {{Option|DEBUG|debugging]] }} is enabled, 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 find a proper good split size. The following example shows how the output can look for creating a database for an XMark document with 111 MB 1 GB, and with 128 MB of available main memoryassigned to the JVM:

> basex -d -c"set ftindexSET FTINDEX ON; create db 111mb 111mbSET TOKENINDEX ON; CREATE DB xmark 1gb.xml"

.... 8132.44 ........................... 76093.83 ms (17824 15634 KB)

.. 979920 ..|....|....|.... 9.81 M operations, 291318941.78 21 ms (44 MB9035 KB). Recommended SPLITSIZE: 25.

.. 381870 .......|......|. 3.82 M operations, 9026.68 ms (8094 KB). Recommended SPLITSIZE: 13.Indexing Tokens...........|...|..... 3.82 M operations, 63010576.61 11 ms (21257 13489 KB). Recommended SPLITSIZE: 13.

.||.||.|.|.|..|...|..|...|.| 3 splits, 12089347 116.33 M operations, 16420146976.47 75 ms (36 76 MB). Recommended SPLITSIZE: 9.

The info string {{Codeoutput can be interpreted as follows: * The vertical bar <code>|3 splits}} </code> indicates that three a partial full-text index structures were structure was written to disk, and : the text index was e.g. split 4 times.* The mean value of the string {{Code|12089347 operationsSPLITSIZE}} tells that the index construction consisted of approximately 12 mio index operations. If we set <code>[[Options#FTINDEXSPLITSIZE|FTINDEXSPLITSIZE]]</code> recommendations can be assigned to the fixed value {{CodeOption|4000000SPLITSIZE}} (12 mio divided by three)option. Please note that the recommendation is only a vague proposal, so try different values if you get main-of-memory errors or a smaller value, we should be able to build the index and circumvent the indexing gets too slow. Greater values will require more main memory heuristics.