Repetitive query recognition and processing

• US 8,914,390 B2
• Filed: 07/12/2011
• Issued: 12/16/2014
• Est. Priority Date: 07/12/2011
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Peek, Daniel Nota
• Primary Examiner(s): DWIVEDI, MAHESH H
• Application Number:
  US13/181,388
• Publication Number:
  US 20130018918A1
• Time in Patent Office: 1,253 Days
• Field of Search: 707/721, 707/758
• US Class Current: 707/758
• CPC Class Codes: G06F 16/24539 using cached or materialised query results

Abstract

Processing repetitive database queries may include receiving a database query having a connection identifier, determining whether a queue for database queries contains an earlier database query matching the received database query, identifying the second database query as matching the first database query if the queue contains an earlier matching database query, receiving query results for the earlier matching database query from a database server, and forwarding query results to the clients associated with both database queries using corresponding connection identifiers.

Claims

1. A non-transitory computer readable medium comprising instructions, the instructions operable when executed by a processor to:

receive a second database query comprising a second connection identifier, the second connection identifier comprising a user identifier, a session identifier, and a database identifier;

determine whether a queue for unexecuted database queries contains a first database query comprising a first connection identifier, the first connection identifier comprising a user identifier, a session identifier, and a database identifier, wherein the user identifier, the session identifier, and the database identifier of the first connection identifier are the same as the user identifier, the session identifier, and the database identifier of the second connection identifier;

if the queue contains the first database query, identify the second database query as being a duplicate of the first database query;

receive one set of query results for the first database query from a database server; and

forward the set of query results to both a first client associated with the first connection identifier and a second client associated with the second connection identifier.

2. The non-transitory computer readable medium of claim 1, wherein the instructions are further operable when executed by the processor to, if the queue does not contain the first database query, add the second database query to the queue.

3. The non-transitory computer readable medium of claim 1, wherein identifying the received database query as being a duplicate of the first database query comprises associating the first database query in the queue with the second connection identifier.

4. The non-transitory computer readable medium of claim 1, wherein the instructions are further operable when executed by the processor to:

receive query results for a third database query, wherein the third database query comprises a third connection identifier;

forward the query results to a third client associated with the third connection identifier.

5. The non-transitory computer readable medium of claim 1, wherein the first client and the second client are web servers.

6. The non-transitory computer readable medium of claim 1, wherein the database server is a Structured Query Language (SQL) database.

7. An apparatus comprising:

an interface operable to receive unexecuted database queries;

a memory operable to store one or more of the received unexecuted database queries in a queue;

a processor communicatively coupled to the interface and the memory, the processor operable to;

receive a second database query comprising a second connection identifier from the interface, the second connection identifier comprising a user identifier, a session identifier, and a database identifier;

determine whether the queue contains a first database query comprising a first connection identifier, the first connection identifier comprising a user identifier, a session identifier, and a database identifier, wherein the user identifier, the session identifier, and the database identifier of the first connection identifier are the same as the user identifier, the session identifier, and the database identifier of the second connection identifier;

if the queue contains the first database query, identify the second database query as being a duplicate of the first database query;

receive one set of query results for the first database query from a database server; and

forward the set of query results to both a first client associated with the first connection identifier and a second client associated with the second connection identifier.

8. The apparatus of claim 7, wherein the processor is further operable to, if the queue does not contain the first database query, add the second database query to the queue.

9. The apparatus of claim 7, wherein identifying the received database query as being a duplicate of the first database query comprises associating the first database query in the queue with the second connection identifier.

10. The apparatus of claim 7, wherein the instructions are further operable when executed by the processor to:

receive query results for a third database query, wherein the third database query comprises a third connection identifier;

forward the query results to a third client associated with the third connection identifier.

11. The apparatus of claim 7, wherein the first client and the second client are web servers.

12. The apparatus of claim 7, wherein the database server is a Structured Query Language (SQL) database.

13. A method, comprising:

receiving a second database query comprising a second connection identifier, the second connection identifier comprising a user identifier, a session identifier, and a database identifier;

determining whether a queue for unexecuted database queries contains a first database query comprising a first connection identifier, the first connection identifier comprising a user identifier, a session identifier, and a database identifier, wherein the user identifier, the session identifier, and the database identifier of the first connection identifier are the same as the user identifier, the session identifier, and the database identifier of the second connection identifier;

if the queue contains the first database query, identifying the second database query as being a duplicate of the first database query;

receiving one set of query results for the first database query from a database server; and

forwarding the set of query results to both a first client associated with the first connection identifier and a second client associated with the second connection identifier.

14. The method of claim 13, further comprising if the queue does not contain the first database query, adding the second database query to the queue.

15. The method of claim 13, wherein identifying the received database query as being a duplicate of the first database query comprises associating the first database query in the queue with the second connection identifier.

16. The method of claim 13, further comprising:

receiving query results for a third database query, wherein the third database query comprises a third connection identifier;

forwarding the query results to a third client associated with the third connection identifier.

17. The method of claim 13, wherein the first client and the second client are web servers.