DYNAMIC LOAD TESTING

• US 20130317781A1
• Filed: 05/25/2012
• Published: 11/28/2013
• Est. Priority Date: 05/25/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Fuchs, Stefan, Moser, Martin
• Granted Patent: US 9,189,371 B2
• Time in Patent Office: Days
• US Class Current: 702/186
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3433 for load management allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029
• CPC Class Codes: G06F 11/3672 Test management

Abstract

A system includes sending of requests to a computing system based on a first number of users associated with a load test, evaluation of one or more characteristics of the computing system while sending the requests, determination to modify the first number of users to a second number of users based on the one or more evaluated characteristics, and sending of requests to the computing system based on the second number of users.

Claims

1. A method implemented by a computing system in response to execution of program code by a processor of the computing system, the method comprising:

sending requests to a computing system based on a first number of users associated with a load test;

evaluating one or more characteristics of the computing system while sending the requests;

determining to modify the first number of users to a second number of users based on the one or more evaluated characteristics; and

sending requests to the computing system based on the second number of users.

2. A method according to claim 1, wherein the characteristic indicates a usage level of one or more system resources of the computing system.

3. A method according to claim 1, wherein sending requests to the computing system based on the first number of users associated with the load test comprises:

sending requests to the computing system based on the first number of users associated with the load test for a predetermined time period.

4. A method according to claim 1, further comprising:

determining whether to abort and restart the load test based on a number of times users have been added to the load test.

5. A method according to claim 1, wherein determining to modify the first number of users comprises:

determining whether a value of one or more of the evaluated characteristics has reached a threshold.

6. A method according to claim 5, further comprising:

determining that the threshold has been reached; and

continuing to send requests to the computing system based on the current number of users for a predetermined time period.

7. A method according to claim 6, further comprising:

adding a third number of users to the load test;

sending requests to the computing system based on a second current number of users associated with the load test for a second predetermined time period;

removing a fourth number of users from the load test; and

sending requests to the computing system based on a third current number of users associated with the load test for a third predetermined time period.

8. A non-transitory medium storing computer-executable program code, the program code executable by a computing device to:

send requests to a computing system based on a first number of users associated with a load test;

evaluate one or more characteristics of the computing system while sending the requests;

determine to modify the first number of users to a second number of users based on the one or more evaluated characteristics; and

send requests to the computing system based on the second number of users.

9. A medium according to claim 8, wherein the characteristic indicates a usage level of one or more system resources of the computing system.

10. A medium according to claim 8, wherein the sending of requests to the computing system based on the first number of users associated with the load test comprises:

sending of requests to the computing system based on the first number of users associated with the load test for a predetermined time period.

11. A medium according to claim 8, the program code further executable by a computing device to:

determine whether to abort and restart the load test based on a number if times users have been added to the load test.

12. A medium according to claim 8, the program code to determine to modify the first number of users further executable by a computing device to:

determine whether a value of one or more of the evaluated characteristics has reached a threshold.

13. A medium according to claim 12, the program code further executable by a computing device to:

determine that the threshold has been reached; and

continue to send requests to the computing system based on the current number of users for a predetermined time period.

14. A medium according to claim 13, the program code further executable by a computing device to:

add a third number of users to the load test;

send requests to the computing system based on a second current number of users associated with the load test for a second predetermined time period;

remove a fourth number of users from the load test; and

send requests to the computing system based on a third current number of users associated with the load test for a third predetermined time period.

15. A system comprising:

a computing system comprising a first processor and a first memory; and

a testing system comprising a second processor and a second memory, the testing system to;

send requests to a computing system based on a first number of users associated with a load test;

evaluate one or more characteristics of the computing system while sending the requests;

determine to modify the first number of users to a second number of users based on the one or more evaluated characteristics; and

send requests to the computing system based on the second number of users.

16. A system according to claim 15, wherein the sending of requests to the computing system based on the first number of users associated with the load test comprises:

sending of requests to the computing system based on the first number of users associated with the load test for a predetermined time period.

17. A system according to claim 15, the testing system further to:

determine whether to abort and restart the load test based on a number if times users have been added to the load test.

18. A system according to claim 15, wherein the determination to modify the first number of users comprises:

determination of whether a value of one or more of the evaluated characteristics has reached a threshold.

19. A system according to claim 18, the testing system further to:

determine that the threshold has been reached; and

continue to send requests to the computing system based on the current number of users for a predetermined time period.

20. A system according to claim 19, the testing system further to:

add a third number of users to the load test;

send requests to the computing system based on a second current number of users associated with the load test for a second predetermined time period;

remove a fourth number of users from the load test; and

send requests to the computing system based on a third current number of users associated with the load test for a third predetermined time period.