Bureaucrats, editor, reviewer, Administrators
13,550
edits
Changes
Jump to navigation
Jump to search
→Performance
> basex -d -c"SET FTINDEX ON; SET TOKENINDEX ON; CREATE DB xmark 1gb.xml"
Creating Database...
................................ 7609376559.83 99 ms (15634 29001 KB)
Indexing Text...
....|....|...|..|...|. 9.81 M operations, 1894118576.21 92 ms (9035 13523 KB). Recommended SPLITSIZE: 2520.
Indexing Attribute Values...
.........|......|. 3.82 M operations, 90267151.68 77 ms (8094 6435 KB). Recommended SPLITSIZE: 1320.
Indexing Tokens...
.......|..|...|...|.. 3.82 M operations, 105769636.11 73 ms (13489 10809 KB). Recommended SPLITSIZE: 1310.
Indexing Full-Text...
.|.|.||.|.|.|..|...|..|.|..|.| 116.33 M operations, 146976138740.75 94 ms (76 106 MB). Recommended SPLITSIZE: 912.
</pre>
The output can be interpreted as follows:
* The vertical bar <code>|</code> indicates that a partial index structure was written to disk: the text index was e.g. split 4 times.* The mean value of the {{Code|SPLITSIZE}} recommendations can be assigned to the {{Option|SPLITSIZE}} option. Please note that the recommendation is only a vague proposal, so try different values if you get main-of-memory errors or indexing gets too slow. Greater values will require more main memory.* In the example, the full-text index was split 12 times. 116 million tokens were indexed, processing time was 2,5 minutes, and final main memory consumption (after writing the index to disk) was 76 MB. A good value for the split size option could be {{Code|15}}.
=Updates=
