This is an old revision of the document!


Administration: Omnidex Indexing

Indexing Creation

Performance

Omnidex puts on premium on indexing performance. Applications often use hundreds of Omnidex indexes, and so it is important that all of these indexes can be built quickly. Omnidex also puts a premium on index size. Omnidex uses compression algorithms to make the indexes as small as possible while still allowing fast access. This allows the index to be quickly retrieved from the disk, and it also insures that memory usage is kept at a minimum. This improves performance by insuring the fastest I/O and insuring the most caching.

The help insure performance, administrators should maintain the Omnidex indexes on disk drives that are regularly defragmented, and have plenty of extra space. It is also valuable to isolate Omnidex indexes onto a separate disk drive, and even a separate disk controller, than the data files and the temporary file directory. In an ideal world, each of these three kinds of file would have their own drive and their own disk controller to minimize disk contention.

Predicting Indexing Time

(Number of rows) + (Number of prejoined rows) + (Number of keywords)


                  1 billion keywords per hour

Additional Resources

See also:

 
Back to top
admin/indexing/creation/performance.1327613432.txt.gz ยท Last modified: 2016/06/28 22:38 (external edit)