Optimization Of Search Requests
Azure search for high frequency of queries and controlled queries
If too many outstanding requests are received or a target delay is exceeded due to the increased demand burden, delays can be reduced by one of the two ways.
- Increase the number of sprays♪ The belt is a copy of your data, allowing Poscu Azure to balance the demand load by sharing it among several copies. All load-balancing and replication operations between the lines are managed by Posque Azure, and at any time the number of relays allocated to your service can be changed. You can set up up up to 12 relays for the Standard level search service and up to 3 rehearsals for the Bazone level search. Replications can be changed on the Azure portal or PowerShell.
- Raise the search level. Azure is searched at several levels, each offering different levels of productivity. In some cases, the number of requests may exceed the current level of capacity, leading to unacceptable delays even with the maximum number of extensions. In this case, one of the higher levels of search for Azure, such as S3, is well suited for scenarios with a large number of documents and extremely high workloads of requests.
Azure search for slow individual requests
Another possible reason for the high delays is that it is too long to execute a single request. In this case, the addition of the cap will not reduce delays. Two options are available.
