This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:optimization:plans:example [2012/02/03 19:52] doc |
admin:optimization:plans:example [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 370: | Line 370: | ||
| === Step 5: Aggregate counts in the INDIVIDUALS table=== | === Step 5: Aggregate counts in the INDIVIDUALS table=== | ||
| - | Omnidex will aggregate counts in the INDIVIDUALS table by scanning its indexes and filering the results using the index pointers set aside from the previous steps. | + | Omnidex will aggregate counts in the INDIVIDUALS table using indexes on the GROUP BY columns, while also intersecting with the index pointers that were isolated while processing criteria and table joins. |
| <html> | <html> | ||
| Line 449: | Line 449: | ||
| === Step 6: Return the final result set === | === Step 6: Return the final result set === | ||
| - | Omnidex will finally return the result set of the query. When possible, Omnidex will return the first rows as soon as they are available, even if the later rows are still being processed. This speeds query execution, and also helps when only the first screenfuls of data are going to be requested. | + | Omnidex will finally return the result set of the query. When possible, Omnidex will return the first rows as soon as they are available, even if the later rows are still being processed. This speeds query execution, and also helps when only the first screenfuls of data are going to be viewed. |
| <html> | <html> | ||
| Line 535: | Line 535: | ||
| ====== Additional Resources ====== | ====== Additional Resources ====== | ||
| See also: | See also: | ||
| - | {{page>:admin:indexing:see_also&nofooter&noeditbtn}} | + | {{page>:admin:optimization:see_also&nofooter&noeditbtn}} |
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||