From a97cbf842b49d475a405cb4aecce42dba1e22218 Mon Sep 17 00:00:00 2001 From: Jason Stirnaman Date: Tue, 12 Aug 2025 18:20:35 -0500 Subject: [PATCH] chore(influxdb3-dist): Add note about concurrent query exec --- .../influxdb3-query-guides/query-timeout-best-practices.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/shared/influxdb3-query-guides/query-timeout-best-practices.md b/content/shared/influxdb3-query-guides/query-timeout-best-practices.md index fa03dd57a..c101123c7 100644 --- a/content/shared/influxdb3-query-guides/query-timeout-best-practices.md +++ b/content/shared/influxdb3-query-guides/query-timeout-best-practices.md @@ -33,6 +33,12 @@ Optimal timeouts are: InfluxDB 3 uses round-robin query routing to balance load across multiple queriers. This creates a "checkout line" effect that influences timeout strategy. +> [!Note] +> #### Concurrent query execution +> +> InfluxDB 3 supports concurrent query execution, which helps minimize the impact of intensive or inefficient queries. +> However, you should still use appropriate timeouts and optimize your queries for best performance. + ### The checkout line analogy Consider a grocery store with multiple checkout lines: