Managing computing resources

• US 10,162,726 B2
• Filed: 01/18/2011
• Issued: 12/25/2018
• Est. Priority Date: 01/18/2011
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Albrecht, Scott A., Davidson, Joshua
• Primary Examiner(s): Yen, Syling
• Assistant Examiner(s): Tran, Bao G
• Application Number:
  US13/008,178
• Publication Number:
  US 20120185462A1
• Time in Patent Office: 2,898 Days
• Field of Search: 707661, 707718, 707667, 707769, 715736, 715747, 715751, 715780, 715781
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/88 Monitoring involving counting

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium are disclosed. In one aspect, a method includes filtering a first plurality of requests based on one or more criteria to generate first filtered requests, the first plurality of requests being associated with a first query plan that is associated with a first instance, identifying a first application associated with at least a portion of the first filtered requests, and determining a quantity of cores used by the first application based at least in part on the portion of the first filtered requests associated with the first application.

Claims

1. A computer-implemented method comprising:

receiving, by a computing system, a request to determine a quantity of cores of one or more multi-core central processing units included in a first server that are being used by a first application executing within a first instance hosted on the first server;

obtaining, by the computing system, a first request table for the first instance that includes (i) a status indicator for each of a first plurality of requests associated with a first query plan, wherein the first query plan defines a set of operations for retrieving data from a database, and (ii) a type of request indicator associated with each of the first plurality of requests;

filtering, by the computing system, the first plurality of requests associated with the first query plan to determine first filtered requests, wherein the filtering includes determining the first filtered requests that are both;

i) currently executing requests, as indicated by the status indicators, and ii) application requests that are not system requests, as indicated by the type of request indicators;

determining, by the computing system, a quantity of the first filtered requests that are associated with the first application;

determining, by the computing system, that the quantity of the first filtered requests associated with the first application is the quantity of cores used by the first application executing within the first instance on the first server; and

providing, for output by the computing system, the quantity of the first filtered requests associated with the first application as the quantity of the cores used by the first application executing within the first instance on the first server.

2. The method of claim 1, further comprising processing one or more Structured Query Language (SQL) statements to generate the first query plan.

3. The method of claim 1, wherein:

a status indicator of the second subset of requests indicates the request is associated with system databases or non-application databases.

4. The method of claim 1, wherein the filtering comprises excluding requests based on business rules.

5. The method of claim 1, further comprising:

identifying, by the computing system, respective database identifications for each of the first filtered requests based on information associated with each respective first filtered request.

6. The method of claim 5, wherein identifying respective database identifications for the first filtered requests comprises identifying, by the computing system, respective database names for each of the first filtered requests based at least in part on the respective database identifications.

7. The method of claim 6, further comprising:

determining, by the computing system, that the first application is one of a plurality of applications identified as being associated with each of the first filtered requests based at least in part on the respective database names for each of the first filtered requests.

8. The method of claim 1, further comprising:

receiving, by the computing system, a request to determine a quantity of cores of one or more multi-core central processing units included in a second server that are being used by the first application executing within a second instance hosted on the second server;

obtaining, by the computing system, a second request table for the second instance that includes (i) a status indicator for each of a second plurality of requests associated with a second query plan, wherein the second query plan defines a set of operations for retrieving data from the database, and (ii) a type of request indicator associated with each of the second plurality of requests;

filtering, by the computing system, the second plurality of requests associated with the second query plan to determine second filtered requests associated with the first application, wherein the filtering excludes;

a third subset of requests that are in a not-currently-executing status, as indicated by the status indicators, and a fourth subset of requests that are of a system request type, as indicated by the type of request indicators;

determining, by the computing system, a quantity of the second filtered requests that are associated with the first application;

determining, by the computing system, that the quantity of the second filtered requests is the quantity of cores used by the first application executing within the second instance on the second server; and

providing, for output by the computing system, the quantity of the second filtered requests associated with the first application as the quantity of cores used by the first application executing within the second instance on the second server.

9. The method of claim 8, further comprising:

determining, by the computing system, an aggregate quantity of cores used by the first application by aggregating the quantity of cores used by the first application executing within the first instance and the quantity of cores used by the first application executing within the second instance; and

outputting, by the computer system, the aggregate quantity of cores used by the first application.

10. The method of claim 9, further comprising:

providing a graphical representation of the aggregate quantity of cores used by the first application.

11. The method of claim 9, further comprising:

generating a notification if one of the quantity of cores used by the first application executing within the first instance, the quantity of cores used by the first application executing within the second instance, or the aggregate quantity of cores used by the first application exceeds a threshold value.

12. The method of claim 9, further comprising:

billing, by the computing system, a client associated with the first application based on one of the quantity of cores used by the first application executing within the first instance, the quantity of cores used by the first application executing within the second instance, or the aggregate quantity of cores used by the first application.

13. The method of claim 12, wherein billing the client further comprises multiplying the quantity of cores used by the first application executing within the first instance, the quantity of cores used by the first application executing within the second instance, or the aggregate quantity of cores used by the first application by a cost-per-core.

14. The method of claim 8, wherein:

the first server and the second server are included in a computing matrix; and

the first instance and the second instance are associated with the computing matrix.

15. The method of claim 14, wherein the first server and the second server are a single server.

16. The method of claim 1, further comprising:

providing a graphical representation of the quantity of cores used by the first application executing within the first instance.

17. A system comprising:

one or more computers; and

a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations comprising;

receiving, by a computing system, a request to determine a quantity of cores of one or more multi-core central processing units included in a first server that are being used by a first application executing within a first instance hosted on the first server;

obtaining, by the computing system, a first request table for the first instance that includes (i) a status indicator for each of a first plurality of requests associated with a first query plan, wherein the first query plan defines a set of operations for retrieving data from a database, and (ii) a type of request indicator associated with each of the first plurality of requests;

filtering, by the computing system, the first plurality of requests associated with the first query plan to determine first filtered requests, wherein the filtering includes determining the first filtered requests that are both;

i) currently executing requests, as indicated by the status indicators, and ii) application requests that are not system requests, as indicated by the type of request indicators;

determining, by the computing system, a quantity of the first filtered requests that are associated with the first application;

determining, by the computing system, that the quantity of the first filtered requests associated with the first application is the quantity of cores used by the first application executing within the first instance on the first server; and

providing, for output by the computing system, the quantity of the first filtered requests associated with the first application as the quantity of the cores used by the first application executing within the first instance on the first server.

18. The system of claim 17, further comprising:

receiving, by the computing system, a request to determine a quantity of cores of one or more multi-core central processing units included in a second server that are being used by the first application executing within a second instance hosted on the second server;

obtaining, by the computing system, a second request table for the second instance that includes (i) a status indicator for each of a second plurality of requests associated with a second query plan, wherein the second query plan defines a set of operations for retrieving data from the database, and (ii) a type of request indicator associated with each of the second plurality of requests;

filtering, by the computing system, the second plurality of requests associated with the second query plan to determine second filtered requests associated with the first application, wherein the filtering excludes;

a third subset of requests that are in a not-currently-executing status, as indicated by the status indicators, and a fourth subset of requests that are of a system request type, as indicated by the type of request indicators;

determining, by the computing system, a quantity of the second filtered requests that are associated with the first application;

determining, by the computing system, that the quantity of the second filtered requests is the quantity of cores used by the first application executing within the second instance on the second server; and

providing, for output by the computing system, the quantity of the second filtered requests associated with the first application as the quantity of cores used by the first application executing within the second instance on the second server.

19. A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:

receiving, by a computing system, a request to determine a quantity of cores of one or more multi-core central processing units included in a first server that are being used by a first application executing within a first instance hosted on the first server;

obtaining, by the computing system, a first request table for the first instance that includes (i) a status indicator for each of a first plurality of requests associated with a first query plan, wherein the first query plan defines a set of operations for retrieving data from a database, and (ii) a type of request indicator associated with each of the first plurality of requests;

filtering, by the computing system, the first plurality of requests associated with the first query plan to determine first filtered requests, wherein the filtering includes determining the first filtered requests that are both;

i) currently executing requests, as indicated by the status indicators, and ii) application requests that are not system requests, as indicated by the type of request indicators;

determining, by the computing system, a quantity of the first filtered requests that are associated with the first application;

determining, by the computing system, that the quantity of the first filtered requests associated with the first application is the quantity of cores used by the first application executing within the first instance on the first server; and

providing, for output by the computing system, the quantity of the first filtered requests associated with the first application as the quantity of the cores used by the first application executing within the first instance on the first server.

20. The computer storage medium of claim 19, the operations further comprising:

receiving, by the computing system, a request to determine a quantity of cores of one or more multi-core central processing units included in a second server that are being used by the first application executing within a second instance hosted on the second server;

obtaining, by the computing system, a second request table for the second instance that includes (i) a status indicator for each of a second plurality of requests associated with a second query plan, wherein the second query plan defines a set of operations for retrieving data from the database, and (ii) a type of request indicator associated with each of the second plurality of requests;

filtering, by the computing system, the second plurality of requests associated with the second query plan to determine second filtered requests associated with the first application, wherein the filtering excludes;

a third subset of requests that are in a not-currently-executing status, as indicated by the status indicators, and a fourth subset of requests that are of a system request type, as indicated by the type of request indicators;

determining, by the computing system, a quantity of the second filtered requests that are associated with the first application;

determining, by the computing system, that the quantity of the second filtered requests is the quantity of cores used by the first application executing within the second instance on the second server; and

providing, for output by the computing system, the quantity of the second filtered requests associated with the first application as the quantity of cores used by the first application executing within the second instance on the second server.