Azure 搜索中的限制搜索查询是什么？
What is throttled search query in azure search?
我正在为我的应用程序使用 Azure 搜索，但最近我遇到了性能问题。
目前我正在调查问题并且发现了以下文章：
它说：
Scaling Azure Search for high query rates and throttled requests
When you are receiving too many throttled requests or exceed your target
latency rates from an increased query load, you can look to decrease
latency rates in one of two ways: Increase Replicas: A replica is like
a copy of your data allowing Azure Search to load balance requests
against the multiple copies. All load balancing and replication of
data across replicas is managed by Azure Search and you can alter the
number of replicas allocated for your service at any time. You can
allocate up to 12 replicas in a Standard search service and 3 replicas
in a Basic search service. Replicas can be adjusted either from the
Azure portal or PowerShell. Increase Search Tier: Azure Search comes
in a number of tiers and each of these tiers offers different levels
of performance. In some cases, you may have so many queries that the
tier you are on cannot provide sufficiently low latency rates, even
when replicas are maxed out. In this case, you may want to consider
leveraging one of the higher search tiers such as the Azure Search S3
tier that is well suited for scenarios with large numbers of documents
and extremely high query workloads.
现在我不明白限制请求是什么意思。
Google 没有帮助！
当错误率（请求失败并返回 207 或 503 状态代码）超过特定阈值时，Azure 搜索开始限制请求。最好的策略是对 207 和 503 响应使用指数重试策略来控制负载并完全避免节流。
受限请求的 throttle-reason 响应 header 包含有关请求受限原因的信息。看来我们还没有记录下来；我们会努力解决这个问题。
我正在为我的应用程序使用 Azure 搜索，但最近我遇到了性能问题。 目前我正在调查问题并且发现了以下文章：
它说：
Scaling Azure Search for high query rates and throttled requests
When you are receiving too many throttled requests or exceed your target latency rates from an increased query load, you can look to decrease latency rates in one of two ways: Increase Replicas: A replica is like a copy of your data allowing Azure Search to load balance requests against the multiple copies. All load balancing and replication of data across replicas is managed by Azure Search and you can alter the number of replicas allocated for your service at any time. You can allocate up to 12 replicas in a Standard search service and 3 replicas in a Basic search service. Replicas can be adjusted either from the Azure portal or PowerShell. Increase Search Tier: Azure Search comes in a number of tiers and each of these tiers offers different levels of performance. In some cases, you may have so many queries that the tier you are on cannot provide sufficiently low latency rates, even when replicas are maxed out. In this case, you may want to consider leveraging one of the higher search tiers such as the Azure Search S3 tier that is well suited for scenarios with large numbers of documents and extremely high query workloads.
现在我不明白限制请求是什么意思。 Google 没有帮助！
当错误率（请求失败并返回 207 或 503 状态代码）超过特定阈值时，Azure 搜索开始限制请求。最好的策略是对 207 和 503 响应使用指数重试策略来控制负载并完全避免节流。
受限请求的 throttle-reason 响应 header 包含有关请求受限原因的信息。看来我们还没有记录下来；我们会努力解决这个问题。