Datasources: Add concurrency number to the settings #81212
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this feature?
Currently, only Loki (soon InfluxDB for
influxql
) is supporting concurrent query execution. Concurrency allows us to execute queries in parallel.Currently, data sources that use concurrency have a hard-coded concurrent query limit. This must be configurable.
Loki concurrency: #74064
InfluxDB concurrency: #81209
Why do we need this feature?
To be able to execute and return responses faster for the requests that have many queries.
Who is this feature for?
For the users that need to run multiple queries in one panel.
⚠️ Concurrency support is on the data source level. Concurrency must be supported by data sources.
Please refer data source documentation for more information
Special notes for your reviewer:
This setting option is not being used anywhere yet. After having this in place Loki and InfluxDB will start using this.
Please check that: