Azure AI Search Solution

By Ashwin Venugopal -

 




Optimize Performance of an Azure AI Search Solution

The size and complexity of your indexes may affect search solutions’ performance. Additionally, You also need to know how to write efficient queries to search it and choose the right service tier.

Measure Your Current Search Performance

If you don't know how well your search service works, you can't optimize. Establish a baseline performance benchmark so you can verify the advancements you achieve and monitor any decline in performance over time.

To start with, enable diagnostic logging using Log Analytics:

  1. In the Azure portal, select Diagnostic settings.
  2. Give your diagnostic setting a name.
  3. Select allLogs and AllMetrics.
  4. Select Send to Log Analytics workspace.
  5. Choose, or create, your Log Analytics workspace.

This diagnostic data must be recorded at the search service level. Your end users or apps may experience performance problems in a number of locations. If you can demonstrate that your search service is operating efficiently, you may rule it out as a potential cause of performance problems.

Check If Your Search Service Is Throttled

Azure AI can be throttled. A 503 HTTP response is recorded in Log Analytics if your users' or apps' searches are being blocked. Your indexes will seem as 207 HTTP replies if they are being throttled.

This query you can run against your search service logs shows you if your search serviceis being throttled. Choose Logs under Monitoring in the Azure interface. This Kusto query would be used in the New Query 1 tab. You'd run the command to see a bar chart of your search services HTTP responses.

Check Performance Of Individual Queries

The most effective method to evaluate the performance of individual queries is by using a client tool such as Postman. Any tool that displays the headers in the response to a query can be utilized. Azure AI Search consistently provides an 'elapsed-time' value indicating the duration it took for the service to process the query. To calculate the total time it takes to send and receive the response from the client, you can subtract the elapsed time from the overall round trip.

Conclusion

We have successfully learnt about optimizing an Azure AI Search Solution.

 























Comments

Post a Comment

Popular posts from this blog

Connect Data to Azure Sentinel Using Data Connectors

By Ashwin Venugopal -
Image
  Ingest Log Data with Data Connectors You should connect your data sources with Azure Sentinel Connectors to collect the log data whose page displays a growing list of the connectors provided by Azure Sentinel, after selecting the Open connector page (the detailed connector page has a left and right blade).  The information about the connector, the connector's status, and the last time a log was received if connected is provided by the left blade. Whereas the right tab has two tabs- Instructions and Next Steps. The instructions tab can be different based on the connector having Prerequisites and Configuration which can be followed to connect to the data source. The Next Steps tab offers a quick reference to workbooks, query samples, and analytical templates. Data connectors can only be disconnected/deactivated, not deleted. Note-  The connector does not install Workbooks and Analytical Templates as they are already available in the Sentinel environment for out of the box...
Read more

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more

Azure AI Search plugin in Microsoft Security Copilot (Preview)

By Ashwin Venugopal -
Image
  Introduction Azure AI Search is a service that allows to reliably extract content search, extract, and understand at scale. It is typically used to search for documents, data surveys, and chat-style Copilot apps over proprietary data. Indexing and querying are Azure AI Search's two main workloads. While querying allows to search the content from index, indexing loads the content into the search engine and makes it searchable. By connecting to one of the Azure AI Search indexes from within Copilot, the Microsoft Security Copilot integration for Azure enables to use the content in Copilot to produce contextualized, pertinent, and targeted responses.  Requirement Before using the Azure AI Search plugin in Copilot, the desired Azure AI Search index to connect to Copilot is configured as follows: The text field must be searchable.  The title field must be filterable. The vector-field must use text-embedding-ada-002. Integrated vectorization can be used to setup an index in t...
Read more