| | 1 | = Index search = |
| | 2 | "The purpose of storing an index is to optimize speed and performance in finding relevant documents for a search query.Without an index, the search engine would [http://en.wikipedia.org/wiki/Lexical_analysis scan] every document in the corpus, which would require considerable time and computing power. For example, while an index of 10,000 documents can be queried within milliseconds, a sequential scan of every word in 10,000 large documents could take hours. The additional computer storage required to store the index, as well as the considerable increase in the time required for an update to take place, are traded off for the time saved during information retrieval." |
| | 3 | |
| | 4 | === Documentation === |
| | 5 | http://www.molgenis.org/wiki/IndexBasedSearch |
| | 6 | |
| | 7 | == Index Design Factors == |
| | 8 | === '''Merge factors ''' === |
| | 9 | Which features are selected to enter the index. This is configurable through the configuration file in the plugin ,^ ^ |
| | 10 | |
| | 11 | Storage techniques:: How to store the index [http://en.wikipedia.org/wiki/Data data] , that is, whether information should be data compressed or filtered. |
| | 12 | |
| | 13 | |
| | 14 | Index size:: How much computer storage is required to support the index. |
| | 15 | Lookup speed:: How quickly a word can be found in the inverted index. The speed of finding an entry in a data structure, compared with how quickly it can be updated or removed, is a central focus of computer science. |
| | 16 | Maintenance:: How the index is maintained over time.^ [http://en.wikipedia.org/wiki/Index_(search_engine)#cite_note-5 "[6]"] ^ |
| | 17 | Fault tolerance:: |
