Application and method for benchmarking a database server

• US 5,819,066 A
• Filed: 02/28/1996
• Issued: 10/06/1998
• Est. Priority Date: 02/28/1996
• Status: Expired due to Term

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Electronic Data Systems Corporation (Perspecta, Inc.)
• Inventors: Bromberg, Richard N., Kupcunas, Richard W.
• Primary Examiner(s): Bowler, Alyssa H.
• Assistant Examiner(s): FOLLANSBEE, JOHN A
• Application Number:
  US08/608,070
• Time in Patent Office: 951 Days
• Field of Search: 395/500, 395/613, 395/183.09, 395/184.01, 395/920, 395/704, 395/602, 395/670, 395/672
• US Class Current: 707/827
• CPC Class Codes: G06F 11/3428 Benchmarking
• CPC Class Codes: Y10S 706/92 Simulation
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

A benchmarking application for testing the performance of a database server (14) includes a plurality of execution parameters (82) and a program (78) operable to read the execution parameters (82). Processes (56, 58, 60) are generated by the program (78) in accordance with the execution parameters (82). Each process (56, 58, 60) represents a user (16, 18, 20) of the database server (14) and generates benchmark transactions (108) for submission to the database server (14).

Claims

1. A benchmarking application for testing the performance of a database server, comprising:

a plurality of execution parameters;

a program operable to read the execution parameters; and

a plurality of processes generated by the program according to the execution parameters, each process generated to represent a particular user of the database server and operable to generate benchmark transactions for communication to the database server as a repeatable sequence of queries, the benchmark transactions being communicated to the database server in a selected reproducible transaction sequence for each user, the communicated benchmark transactions for all users collectively testing the performance of database-specific activity by the database server.

2. The application of claim 1, wherein the execution parameters specify a predetermined number of users of the database server.

3. The application of claim 1, wherein the application is operable to communicate benchmark transactions to the database server in the same reproducible transaction sequence for a particular user each time the performance of the database server is tested.

4. The application of claim 3, wherein the reproducible transaction sequence is specified using a skip algorithm, the skip algorithm at least partially specifying a different reproducible transaction sequence for each user.

5. The application of claim 1, further comprising a plurality of transaction modules associated with each process, each transaction module having an embedded benchmark transaction.

6. The application of claim 1, further comprising a programmatic interface, wherein the benchmark transactions generated by each process may be customized using the programmatic interface.

7. The application of claim 1, further comprising a plurality of connect modules, each process having an associated connect module operable to communicate benchmark transactions from the process to the database server.

8. The application of claim 1, further comprising a plurality of transaction log files, each process having an associated transaction log file operable to store log information concerning the benchmark transactions generated by the process.

9. The application of claim 8, wherein the application is operable to generate analysis reports using the log information stored in the transaction log files.

10. The application of claim 1, further comprising a plurality of template functions for customizing the benchmark transactions communicated to the database server.

11. The application of claim 1, wherein performance of the database server is tested without testing the performance of networks, user interfaces, and user workstations associated with the database server.

12. A system for benchmarking a database server, comprising:

a database;

a database server coupled to the database and operable to serve a plurality of users; and

a plurality of processes, each process representing one of the users of the database server and operable to generate benchmark transactions for communication to the database server as a repeatable sequence of database queries, the benchmark transactions for all users being communicated to the database server according to a specified execution sequence, the benchmark transactions being communicated in a selected pattern and at selected intervals for each user to define a reproducible transaction sequence for each user, the communicated benchmark transactions for all users collectively testing the performance of database-specific activity by the database server.

13. The system of claim 12, wherein the processes run on a first computer and the database server runs on a second computer.

14. The system of claim 12, further comprising a program and a plurality of execution parameters, the program operable to read the execution parameters and to generate the processes in accordance with the execution parameters, wherein the execution parameters specify a predetermined number of users of the database server and specify the particular access of each user to the database server.

15. The system of claim 12, wherein the system is operable to communicate benchmark transactions to the database server in the same reproducible transaction sequence for a particular user each time the database server is tested.

16. The application of claim 15, wherein the reproducible transaction sequence is specified using a skip algorithm, the skip algorithm at least partially specifying a different reproducible transaction sequence for each user.

17. The application of claim 12, further comprising a plurality of transaction log files, each process having an associated transaction log file operable to store log information concerning the benchmark transactions generated by the process.

18. The system of claim 12, further comprising a plurality of template functions for customizing the benchmark transactions communicated to the database server.

19. The system of claim 12, wherein performance of the database server is tested without testing the performance of networks, user interfaces, and user workstations associated with the database server.

20. A method for benchmarking a database server, comprising:

generating a plurality of processes, each of the processes representing a user of the database server;

generating, at the processes, benchmark transactions for the corresponding user, the benchmark transactions being database queries operable to prompt the database server to perform some database-specific activity; and

communicating the benchmark transactions for each user to the database server as a repeatable sequence of database queries, the benchmark transactions being communicated to the database server in a selected reproducible transaction sequence for each user, the communicated benchmark transactions for all users collectively testing the performance of some database-specific activity by the database server.

21. The method of claim 20, further comprising defining a plurality of execution parameters specifying a predetermined number of users of the database server.

22. The method of claim 20, further comprising customizing the benchmark transactions generated by each process using a programmatic interface.

23. The method of claim 20, wherein communicating benchmark transactions to the database server comprises communicating benchmark transactions to the database server in the same reproducible transaction sequence for a particular user each time the database server is benchmarked.

24. The method of claim 20, wherein the step of generating benchmark transactions comprises generating benchmark transactions in a different reproducible transaction sequence for each user, the database queries being communicated to the database server in a different pattern and at different intervals for each user.

25. The method of claim 20, further comprising the step of customizing the benchmark transactions communicated to the database server using template functions.

26. The method of claim 20, wherein performance of the database server is tested without testing the performance of networks, user interfaces, and user workstations associated with the database server.