Collection of performance information for search queries executed in a tiered architecture

• US 8,239,374 B2
• Filed: 01/18/2010
• Issued: 08/07/2012
• Est. Priority Date: 01/18/2010
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Narula, Puneet, Sidhana, Harneet, Mankotia, Risham
• Primary Examiner(s): Pham, Hung Q
• Application Number:
  US12/689,092
• Publication Number:
  US 20110179016A1
• Time in Patent Office: 932 Days
• Field of Search: None
• US Class Current: 707/719
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 16/245 Query processing

Abstract

An execute request is sent to a search component. The execute request specifies a search query. Subsequently, an execute response is received from the search component. The execute response comprising latency data and one or more properties of query results. The latency data specifies an amount of time consumed by the search component to process the execute request. The query results are content items that satisfy the search query. A record object model latency request is sent to the search component. The record object model latency request specifies search performance information based on the latency data. A record interface latency request is sent to the search component. The record interface latency request specifies interface performance information based on an amount of time consumed by the first component to process the search request.

Claims

1. A method of collecting performance information for search queries, the method comprising:

receiving, by a first component, a search request, the search request specifying a search query, the first component provided by a first computing system;

after receiving the search request, sending, by the first component, an execute request to a second component, the execute request being a web services request to invoke an execute method of a web Application Programming Interface (API) provided by the second component, the execute request specifying the search query;

after sending the execute request, receiving, by the first component, an execute response from the second component, the execute response being a web services response that is responsive to the execute request, the execute response comprising latency data and data regarding query results, the latency data specifying an amount of time consumed by the second component to process the execute request, the query results being content items that satisfy the search query;

after receiving the execute response, generating, by the first component, user interface data, the user interface data representing a user interface element having contents that depend on the query results;

sending, by the first component, a record object model latency request to the second component, the record object model latency request being a web services request to invoke a record object model latency method of the web API, the record object model latency request specifying search performance information based on the latency data;

sending, by the first component, a record interface latency request to the second component, the record interface latency request being a web services request to invoke a record interface latency method of the web API, the record interface latency request specifying interface performance information based on an amount of time consumed by the first component to process the search request;

receiving, by the first component, a record object model latency response from the second component, the record object model latency response being a web services response that is responsive to the record object model latency request, the record object model latency response specifying whether verbose query monitoring is turned on at the second component; and

receiving, by the first component, a record interface latency response from the second component, the record interface latency response being a web services response that is responsive to the record interface latency request, the record interface latency response specifying whether verbose query monitoring is turned on at the second component,

wherein, when verbose query monitoring is turned on, the second component stores the following for the search query;

a correlation identifier, a name of a computer that processed the execute request, a number of milliseconds consumed by intermediate processing by the second component in processing the execute request, terms in the search query, and a total time in milliseconds consumed by the second component in processing the execute request.

2. The method of claim 1,

wherein the method further comprises:

sending, by the first component, a plurality of execute requests to the second component within a given time period; and

receiving, by the first component, a plurality of execute responses from the second component, each execute response in the plurality of execute responses being responsive to an execute request in the plurality of execute requests; and

wherein the search performance information is based on latency data in each execute response in the plurality of execute responses.

3. The method of claim 2,

wherein the method further comprises:

receiving, by the first component, a plurality of search requests; and

wherein the interface performance information specifies amounts of time consumed by the first component to process each search request in the plurality of search requests.

4. The method of claim 1,

wherein the method further comprises:

sending, by the first component, a get scopes request to the second component, the get scopes request being a web services request to invoke a get scopes method of the web API; and

receiving, by the first component, a get scopes response from the second component, the get scopes response being a web services response that is responsive to the get scopes request, the get scopes response specifying a set of available search scopes provided by the second component; and

wherein the execute request specifies at least one search scope in the set of available search scopes.

5. The method of claim 1, further comprising:

sending, by the first component, a record click request to the second component, the record click request being a web services request to invoke a record click method of the web API, the record click request including information describing a click through that has occurred on a given content item, the given content item being one of the query results.

6. The method of claim 1, further comprising:

sending, by the first component, a query suggestions request to the second component, the query suggestions request being a web services request to invoke a query suggestions method of the web API, the query suggestions request specifying one or more properties describing the search query; and

receiving, by the first component, a query suggestions response from the second component, the query suggestions response being a web services response that is responsive to the query suggestions request, the query suggestions response specifying a set of one or more query suggestions, each query suggestion in the set of query suggestions being a search query related to the search query.

7. The method of claim 1,

sending, by the first component, a get properties request to the second component, the get properties request being a web services request to invoke a get properties method of the web API;

and

receiving, by the first component, a get properties response from the second component, the get properties response being a web services response that is responsive to the get properties request, the get properties response containing information about managed properties of the second component.

8. The method of claim 1, wherein the execute response specifies an amount of time consumed by intermediate processing of the execute request at the second component and an amount of time consumed to execute database operations for retrieving the query results from a database.

9. The method of claim 1,

wherein the first component provides a collection of one or more websites to client computing systems;

and

wherein receiving the search request comprises;

receiving the search request through a web page in one of the websites.

10. A computing device comprising:

a processing system; and

a data storage system storing software instructions that, when executed by the processing system, cause the computing device to;

receive an execute request from a front end component, the execute request being a web services request to invoke an execute method of a web Application Programming Interface (API) provided by the computing device, the execute request specifying a search query;

after receiving the execute request, send an execute response to the front end component, the execute response being a web services response that is responsive to the execute request, the execute response comprising latency data and one or more properties of query results, the latency data specifying an amount of time consumed by the computing device to process the execute request, the query results being content items that satisfy the search query;

receive a record object model latency request from the front end component, the record object model latency request being a web services request to invoke a record object model latency method of the web API, the record object model latency request specifying search performance information based on the latency data;

receive a record interface latency request from the front end component, the record interface latency request being a web services request to invoke a record interface latency method of the web API, the record interface latency request specifying interface performance information based on an amount of time consumed by the front end component to process a search request that specifies the search query; and

send a record interface latency response to the front end component, the record interface latency response being a web services response that is responsive to the record interface latency request, the record interface latency response specifying whether verbose query monitoring is turned on.

11. The computing device of claim 10, wherein the software instructions, when executed by the processing system, further cause the computing device to:

use an index to identify the query results; and

retrieve the one or more properties of the query results from a data source component provided by another computing device.

12. The computing device of claim 10, wherein the software instructions, when executed by the processing system, further cause the computing device to:

send a record object model latency response to the front end component, the record object model latency response being a web services response that is responsive to the record object model latency request, the record object model latency response specifying whether verbose query monitoring is turned on; and

wherein when verbose query monitoring is turned on, the record interface latency request includes the following for the search query;

a correlation identifier, a name of a computer that processed the execute request, a number of milliseconds consumed by intermediate processing by the computing device in processing the execute request, terms in the search query, and a total time in milliseconds consumed by the computing device in processing the execute request.

13. The computing device of claim 10,

wherein the software instructions, when executed by the processing system, cause the computing device to:

receive a plurality of execute requests from the front end component; and

send a plurality of execute responses to the front end component; and

wherein the search performance information is based on latency data in each execute response in the plurality of execute responses received by the front end component in a given time period.

14. The computing device of claim 13, wherein the interface performance information specifies amounts of time consumed by the front end component to process each search request in a plurality of search requests received in the given time period.

15. The computing device of claim 10,

wherein the software instructions, when executed by the processing system, cause the computing device to:

receive a get scopes request from the front end component, the get scopes request being a web services request to invoke a get scopes method of the web API; and

send a get scopes response to the front end component, the get scopes response being a web services response that is responsive to the get scopes request, the get scopes response specifying a set of available search scopes provided by the computing device; and

wherein the execute request specifies at least one search scope in the set of available search scopes.

16. The computing device of claim 10, wherein the software instructions, when executed by the processing system, cause the computing device to receive a record click request from the front end component, the record click request being a web services request to invoke a record click method of the web API, the record click request including information describing a click through that has occurred on one of the query results.

17. The computing device of claim 10, wherein the software instructions, when executed by the processing system, cause the computing device to:

receive a query suggestions request from the front end component, the query suggestions request being a web services request to invoke a query suggestions method of the web API, the query suggestions request specifying one or more properties describing the search query; and

send a query suggestions response to the front end component, the query suggestions response being a web services response that is responsive to the query suggestions request, the query suggestions response specifying a set of one or more query suggestions, each query suggestion in the set of query suggestions being a search query related to the search query.

18. The computing device of claim 10, wherein the software instructions, when executed by the processing system, cause the computing device to:

receive a get click frequencies request from the front end component, the get click frequencies request being a web services request to invoke a get click frequencies method of the web API, the get click frequencies request specifying a Uniform Resource Identifier (URI); and

send a get click frequencies response to the front end component, the get click frequencies response being a web services response that is responsive to the get click frequencies request, the get click frequencies response containing click frequencies for the URI.

19. A computer-readable data storage medium comprising software instructions that, when executed, cause a computing device to:

provide a collection of one or more websites to client computing systems;

receive a search request through a web page in one of the websites, the search request specifying a search query;

after receiving the search request, send an execute request to a search component provided by another computing device, the execute request being a web services request to invoke an execute method of a web Application Programming Interface (API) provided by the search component, the execute request specifying the search query;

send a query suggestions request to the search component, the query suggestions request being a web services request to invoke a query suggestions method of the web API, the query suggestions request specifying one or more properties describing the search query;

receive a query suggestions response from the search component, the query suggestions response being a web services response that is responsive to the query suggestions request, the query suggestions response specifying a set of one or more query suggestions, each query suggestion in the set of query suggestions being a search query related to the search query;

after sending the execute request, receive an execute response from the search component, the execute response being a web services response that is responsive to the execute request, the execute response comprising latency data and one or more properties of query results, the latency data specifying an amount of time consumed by the search component to process the execute request, an amount of time consumed by intermediate processing of the execute request at the search component and an amount of time consumed to execute database operations for retrieving the query results from a database, wherein the query results are content items that satisfy the search query;

after receiving the execute response, generate a search results page containing at least one of the properties of a given content item, the given content item being one of the query results;

send a record object model latency request to the search component, the record object model latency request being a web services request to invoke a record object model latency method of the web API, the record object model latency request specifying search performance information based on the latency data and based on latency data specified in execute responses for other search requests received within a given time period;

receive a record object model latency response from the search component, the record object model latency response being a web services response that is responsive to the record object model latency request, the record object model latency response specifying whether verbose query monitoring is turned on at the search component;

send a record interface latency request to the search component, the record interface latency request being a web services request to invoke a record interface latency method of the web API, the record interface latency request specifying interface performance information based on amounts of time consumed by the computing device to process the search request and other search requests received in the given time period; and

receive a record interface latency response from the search component, the record interface latency response being a web services response that is responsive to the record interface latency request, the record interface latency response specifying whether verbose query monitoring is turned on at the search component.