This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
admin:indexing:autocomplete:optimization [2011/01/24 15:29] 127.0.0.1 external edit |
admin:indexing:autocomplete:optimization [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| Line 13: | Line 14: | ||
| ---- | ---- | ||
| - | |||
| - | |||
| ==== The Optimization Behind AutoComplete ==== | ==== The Optimization Behind AutoComplete ==== | ||
| + | There is no special optimization that is required to use AutoComplete, other than insuring that these queries are performed against columns indexed with an Omnidex or QuickText index. Note that QuickText indexes require the use of the 'optimization=distinct_key' option as shown on the previous page. | ||
| + | |||
| + | The performance of AutoComplete stems from Omnidex's ability to quickly aggregate data. In AutoComplete queries, Omnidex scans its own indexes to determine the values that match the criteria and return their counts. | ||