PRIORITIZED THROTTLING IN A MULTIUSAGE ENVIRONMENT

• US 20150006710A1
• Filed: 06/26/2013
• Published: 01/01/2015
• Est. Priority Date: 06/26/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Sauerwald, Nikolai, Freidlin, David, Fischer, Andre
• Granted Patent: US 9,992,301 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/0888 Throughput
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

Prioritization criteria can be applied to assign a priority ranking to server processes executed by a backend server, and a utilization of the backend server by server demands can be quantified. Upon determining that the quantified utilization of the backend server has reached or exceeded one or more determined limits on backend utilization, at least a lowest priority server process can be throttled based on one or more throttling parameters.

Claims

1. A computer program product comprising a machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

applying one or more prioritization criteria to assign a priority ranking to each of a plurality of server processes being executed by a backend server;

quantifying a utilization of the backend server by a plurality of server demands, the plurality of server demands comprising the plurality of server processes being executed by the backend server;

determining that the quantified utilization of the backend server has reached or exceeded one or more determined limits on backend utilization; and

throttling at least a lowest priority server process of the plurality of server processes based on one or more throttling parameters.

2. A computer program product as in claim 1, wherein the operations further comprise de-throttling a highest priority, previously throttled server process when the utilization of the backend server has reached or dropped below one or more second limits on backend utilization.

3. A computer program product as in claim 1, wherein the prioritization criteria comprise at least one of a program type, a specific program, a specific user or a group of users, a business case or group of business cases.

4. A computer program product as in claim 1, wherein the quantifying further comprises at least one of determining a percentage of available processor cycles currently in use, determining a number of calls to the backend server per a given unit of time, and using one or more key performance indicators.

5. A computer program product as in claim 1, wherein the one or more throttling parameters are defined universally and/or with one or more aspects that are specific to at least one of a specific server process, a type of server process, a specific user, and a specific type of user.

6. A computer program product as in claim 1, wherein the one or more throttling parameters comprise a plurality of sets of throttling parameters that are applied stepwise as the utilization of the backend server increases.

7. A system comprising:

at least one programmable processor; and

a machine-readable medium storing instructions that, when executed by the at least one programmable processor, cause the at least one programmable processor to perform operations comprising;

applying one or more prioritization criteria to assign a priority ranking to each of a plurality of server processes being executed by a backend server;

quantifying a utilization of the backend server by a plurality of server demands, the plurality of server demands comprising the plurality of server processes being executed by the backend server;

determining that the quantified utilization of the backend server has reached or exceeded one or more determined limits on backend utilization; and

throttling at least a lowest priority server process of the plurality of server processes based on one or more throttling parameters.

8. A system as in claim 7, wherein the operations further comprise de-throttling a highest priority, previously throttled server process when the utilization of the backend server has reached or dropped below one or more second limits on backend utilization.

9. A system as in claim 7, wherein the prioritization criteria comprise at least one of a program type, a specific program, a specific user or a group of users, a business case or group of business cases.

10. A system as in claim 7, wherein the quantifying further comprises at least one of determining a percentage of available processor cycles currently in use, determining a number of calls to the backend server per a given unit of time, and using one or more key performance indicators.

11. A system as in claim 7, wherein the one or more throttling parameters are defined universally and/or with one or more aspects that are specific to at least one of a specific server process, a type of server process, a specific user, and a specific type of user.

12. A system as in claim 7, wherein the one or more throttling parameters comprise a plurality of sets of throttling parameters that are applied stepwise as the utilization of the backend server increases.

13. A computer-implemented method comprising:

applying one or more prioritization criteria to assign a priority ranking to each of a plurality of server processes being executed by a backend server;

quantifying a utilization of the backend server by a plurality of server demands, the plurality of server demands comprising the plurality of server processes being executed by the backend server;

determining that the quantified utilization of the backend server has reached or exceeded one or more determined limits on backend utilization; and

throttling at least a lowest priority server process of the plurality of server processes based on one or more throttling parameters.

14. A computer-implemented method as in claim 13, further comprising de-throttling a highest priority, previously throttled server process when the utilization of the backend server has reached or dropped below one or more second limits on backend utilization.

15. A computer-implemented method as in claim 13, wherein the prioritization criteria comprise at least one of a program type, a specific program, a specific user or a group of users, a business case or group of business cases.

16. A computer-implemented method as in claim 13, wherein the quantifying further comprises at least one of determining a percentage of available processor cycles currently in use, determining a number of calls to the backend server per a given unit of time, and using one or more key performance indicators.

17. A computer-implemented method as in claim 13, wherein the one or more throttling parameters are defined universally and/or with one or more aspects that are specific to at least one of a specific server process, a type of server process, a specific user, and a specific type of user.

18. A computer-implemented method as in claim 13, wherein the one or more throttling parameters comprise a plurality of sets of throttling parameters that are applied stepwise as the utilization of the backend server increases.

19. A computer-implemented method as in claim 13, wherein at least one of the applying, the quantifying, the determining, and the throttling is performed by a system comprising at least one programmable processor.