This shows you the differences between two versions of the page.
|
admin:optimization:config:timeouts [2012/02/13 22:22] doc created |
admin:optimization:config:timeouts [2016/06/28 22:38] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ~~NOTOC~~ | ||
| - | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | |||
| - | ====== Administration: Optimizing Queries ====== | ||
| - | |||
| - | ===== Configuring Omnidex ===== | ||
| - | |||
| - | |||
| - | [[admin:optimization:config:home|Overview]] | | ||
| - | [[admin:optimization:config:optimizations|Optimizations]] | | ||
| - | [[admin:optimization:config:thresholds|Thresholds]] | | ||
| - | **[[admin:optimization:config:timeouts|Timeouts]]** | | ||
| - | [[admin:optimization:config:diagnostics|Diagnostics]] | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ==== Timeouts ==== | ||
| - | |||
| - | 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. | ||
| - | |||
| - | 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. | ||
| - | |||
| - | <code> | ||
| - | select ... with TIMEOUT=30 | ||
| - | </code> | ||
| - | |||
| - | The TIMEOUT can also be set for all queries using the SET TIMEOUT statement. | ||
| - | |||
| - | <code> | ||
| - | set timeout 30 | ||
| - | </code> | ||
| - | |||
| - | ===== ===== | ||
| - | ---- | ||
| - | \\ | ||
| - | **[[admin:optimization:config:timeouts|Next]]** | ||
| - | |||
| - | |||
| - | ====== Additional Resources ====== | ||
| - | See also: | ||
| - | {{page>:admin:optimization:see_also&nofooter&noeditbtn}} | ||
| - | |||
| - | {{page>:bottom_add&nofooter&noeditbtn}} | ||