This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
admin:optimization:config:timeouts [2012/02/13 22:22] doc created |
admin:optimization:config:timeouts [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 19: | Line 19: | ||
| Omnidex can interrupt a query after a certain amount of time has passed. This can be valuable to insure that no single query consumes too much resource on the server. Once the timeout is reached, Omnidex will return an error. This error is an indication that the query may benefit from further optimization. | Omnidex can interrupt a query after a certain amount of time has passed. This can be valuable to insure that no single query consumes too much resource on the server. Once the timeout is reached, Omnidex will return an error. This error is an indication that the query may benefit from further optimization. | ||
| + | |||
| + | Omnidex will enforce timeouts as well as it can; however, at times Omnidex transfer control of the query over to other services, such as the underlying relational database. Omnidex may not be able to interrupt the underlying service. In those cases, Omnidex will trigger the timeout as soon as control is returned. | ||
| Timeouts are not active by default. They can be set using the TIMEOUT option of the SELECT statement. The value used in this option is the number of elapsed seconds before the timeout is reached. | Timeouts are not active by default. They can be set using the TIMEOUT option of the SELECT statement. The value used in this option is the number of elapsed seconds before the timeout is reached. | ||
| Line 35: | Line 37: | ||
| ---- | ---- | ||
| \\ | \\ | ||
| - | **[[admin:optimization:config:timeouts|Next]]** | + | **[[admin:optimization:config:thresholds|Prev]]** | |
| + | **[[admin:optimization:config:diagnostics|Next]]** | ||