DATABASE ENGINE THROTTLING

• US 20110179057A1
• Filed: 01/18/2010
• Published: 07/21/2011
• Est. Priority Date: 01/18/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Wojcik, Justyna W.
• Application Number:
  US12/688,920
• Publication Number:
  US 20110179057A1
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409

Abstract

Architecture that includes a service which ensures that a server database engine handles different types of workload in an optimized manner. The handling includes penalizing (e.g., delaying or rejecting) query requests from a network which would otherwise bring the database engine outside of the limits for which the engine can reliably and consistently handle workloads, and for which the engine is certified. The service provides engine throttling that adapts dynamically to the workload based on the workload type and resource consumption limits. The service can also exclude system critical workloads from throttling and selectively penalize requests based on the request source to provide optimized division of resources between the workloads. The level of throttling can be adjusted according to feedback received from previously-applied actions. The architecture also includes a configuration component external to the engine for the configuration of resource consumption limits and other parameters.

Claims

1. A computer-implemented database management system having a physical storage media, comprising:

a penalty component of a database engine controlled to selectively penalize one or more incoming query requests to impact processing of the one or more requests; and

a throttling service that monitors performance data associated with the database engine and adjusts workloads via the penalty component to maintain engine performance within consumption limits of available resources.

2. The system of claim 1, wherein the throttling service dynamically adjusts handling of the workloads by controlling the penalty component to reject one or more of the query requests in response to changes in the monitored performance data.

3. The system of claim 2, wherein a request is rejected based on request type and on resource consumption for the request type.

4. The system of claim 1, wherein the throttling service further monitors performance data associated with a host system of the database engine and adjusts handling of the workloads via the penalty component based on one or more of the performance data of the host system and database engine to maintain database engine performance within limits of resource consumption.

5. The system of claim 1, wherein the throttling service ignores adjustment of workloads that relate to system critical processes.

6. The system of claim 5, wherein the workloads are categorized into load groups, where a load group defined to include the system critical processes is ignored from throttling.

7. The system of claim 1, wherein the throttling service rejects a request or delays a request based on a source of the request to optimize resource consumption among the workloads and across engine partitions.

8. The system of claim 1, wherein the service computes a trend of resource consumption of an engine partition relative to the limits and throttles back on a workload associated with the partition for which the trend indicates resource consumption will exceed the limits.

9. The system of claim 1, further comprising a configuration component for configuring the limits, the configuration component implemented external to the database engine, which is a relational database engine.

10. A computer-implemented database management system having a physical storage media, comprising:

a penalty component of a database engine controlled to selectively penalize one or more incoming query requests;

a throttling service that monitors performance data associated with the database engine and with a host system, the service adjusts workloads via the penalty component to maintain engine performance within consumption limits of available resources; and

a configuration component for configuring the consumption limits.

11. The system of claim 10, wherein the throttling service dynamically adjusts handling of the workloads by rejecting or delaying a request in response to changes in the monitored performance data, the request rejected or delayed based on request type and on resource consumption for the request type.

12. The system of claim 10, wherein the throttling service ignores the adjustment of workloads that relate to system critical processes.

13. The system of claim 10, wherein the configuration component facilitates automatic adjustment of throttling of the throttling service according to feedback based on previously-applied actions.

14. A computer-implemented database management method that employs a processor and memory, comprising:

monitoring performance data of a database engine as part of processing workloads; and

penalizing workload requests based on the performance data to maintain database engine performance within resource consumption limits.

15. The method of claim 14, further comprising penalizing a request by rejecting or delaying the request based on request type.

16. The method of claim 14, further comprising penalizing a request based on fairness of resource consumption relative to other requests.

17. The method of claim 14, further comprising excluding system critical workloads from penalization based on defined load groups.

18. The method of claim 14, further comprising penalizing a request based on request source to level engine resources across workloads.

19. The method of claim 14, further comprising adjusting penalization of the workload requests based on previous request actions.

20. The method of claim 14, further comprising configuring the resource consumption limits external to the database engine.