Improve doc

Signed-off-by: Marco Pracucci <marco@pracucci.com>
This commit is contained in:
Marco Pracucci 2024-01-26 19:09:29 +01:00
parent 6bbb03bd00
commit 1bb341fa51
No known key found for this signature in database
GPG Key ID: 74C1BD403D2DF9B5
1 changed files with 3 additions and 2 deletions

View File

@ -221,5 +221,6 @@ By default, rule groups execute concurrently, but the rules within a group execu
output of a preceding rule as its input. However, if there is no detectable relationship between rules then there is no output of a preceding rule as its input. However, if there is no detectable relationship between rules then there is no
reason to run them sequentially. reason to run them sequentially.
When the `concurrent-rule-eval` feature flag is enabled, rules without any dependency on other rules within a rule group will be evaluated concurrently. When the `concurrent-rule-eval` feature flag is enabled, rules without any dependency on other rules within a rule group will be evaluated concurrently.
This can improve rule reliability at the expense of adding more concurrent query load. The number of concurrent rule evaluations can be configured This has the potential to improve rule group evaluation latency and resource utilization at the expense of adding more concurrent query load.
with `--rules.max-concurrent-rule-evals` which is set to `4` by default.
The number of concurrent rule evaluations can be configured with `--rules.max-concurrent-rule-evals`, which is set to `4` by default.