Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Ingestion limits
...
Event size
The maximum number size of steps is calculated using the following formula: bound(A, F * len ^E + I, B)
where len is the string length and the rest of parameters are defined by the following pragmas:
re.cut.min
(int4
) is *A*, defaults to 100.re.cut.max
(int4
) is *B*, defaults to infinite.re.cut.factor
(float8
) is *F*, defaults to 2.0.re.cut.exp
(float8
) is *E*, defaults to 3.0/2.re.cut.inc
(float8
) is *I*, defaults to 100.0.
Maximum memory usage
The values are:
Code Block |
---|
~/repos/automation (master=)]$ git grep malote_memory_limit
ansible/environments/aws/ap/pro/group_vars/datanode.yml:malote_memory_limit: "16GB"
ansible/environments/aws/ap/pro/group_vars/datanode.yml:metamalote_memory_limit: "4GB"
ansible/environments/aws/ap/pro/group_vars/metamalote-general.yml:metamalote_memory_limit: "64GB"
ansible/environments/aws/ap/pro/group_vars/metamalote-intermediate-ap2.yml:metamalote_memory_limit: "32GB"
ansible/environments/aws/ap/pro/group_vars/metamalote-intermediate-ap3.yml:metamalote_memory_limit: "32GB"
ansible/environments/aws/ap/pro/group_vars/metamalote.yml:metamalote_memory_limit: "16GB"
ansible/environments/aws/ca/pro/group_vars/datanode-dr-manulife.yml:malote_memory_limit: "16GB"
ansible/environments/aws/ca/pro/group_vars/datanode-dr-manulife.yml:metamalote_memory_limit: "4GB"
ansible/environments/aws/ca/pro/group_vars/datanode.yml:malote_memory_limit: "10GB"
ansible/environments/aws/ca/pro/group_vars/datanode.yml:metamalote_memory_limit: "4GB"
ansible/environments/aws/ca/pro/group_vars/metamalote-dr-manulife.yml:metamalote_memory_limit: "20GB"
... |
Subqueries memory limit
Memory
a single event is 32MB.
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.
...
Limit 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 10 aggregations by default.
There are no limits for the following processes:
Number of reinjections that a customer can create.
Number of query lookups that a customer can create.
Number of Devo Flows that a customer can create.
300 alert definitions