Query engine limits
Below are some limits related to Devo’s query engine. Note that whenever any of these limits are reached, the query is cancelled and a error 109 is returned.
Regex maximum steps
There is a limit based on the number of steps that are required to solve the regex. This limit is calculated using a complex formula and is a function of the string size.
Maximum memory usage
There is a limit in the amount of memory that can be used to calculate aggregations. This limit depends on the number of concurrent queries running at the same time in the platform.
Subqueries memory limit
Subqueries are limited in three different ways:
Max memory
32 KB for a single subquery
64 KB for all subqueries
CPU
10 minutes CPU time
Execution time
The maximum time to run a subquery before finalising is 20 minutes.
Collect operations limit
100,000 elements for collect, collectSorted, collectDistinct and the percentile operations.
Limits related to the number of backend processes that run queries against the query engine
To avoid a potential uncontrolled creation of backend processes, Devo has the following default limits:
A domain can create a maximum of 300 alert definitions