I'm trying to optimize my cluster based on the usage profile. In my scenario, i want to ingest historical data only once, then use the cluster only for running queries. Various factors affect the actual number of requests that can run concurrently on a database.
With weak consistency, the effective default limit on maximum concurrent requests depends on the sku of the cluster and number of query heads, and is calculated as: The most dominant factors are database sku, database's available resources, and. Effectively the document means that ingest capacity (in terms of concurrent ingest operations) is 3/4 times the overall number of cores in the cluster, but not higher than 512.
It's possible that kusto is generally answering your queries faster than they are being submitted. Discover how to assign security roles to users, groups, and apps for. The effective value for concurrent operations per node is automatically adjusted by the system in the range [minimumconcurrentoperationspernode, maximumconcurrentoperationspernode],. In this article, you learn to optimize your azure data explorer setup for high concurrency.