Application workload capture and replay system

• US 8,380,665 B2
• Filed: 03/30/2011
• Issued: 02/19/2013
• Est. Priority Date: 02/24/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Papadomanolakis, Efstratios, Cai, Zhongtang, Colle, Romain, Dageville, Benoit, Dias, Karl, Galanis, Leonidas, Graham, Rodney, Gong, Bo, Altmar, Qinghui H., Yoon, Jae Young, Fidanboylu, Mehmet, Hsu, Tom
• Primary Examiner(s): LE, HUNG D
• Application Number:
  US13/076,313
• Publication Number:
  US 20120221519A1
• Time in Patent Office: 692 Days
• Field of Search: None
• US Class Current: 707/615
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites

Abstract

An application workload capture and replay system with a transactionally consistent application workload replay feature is provided. More particularly, the feature includes capture-phase components for capturing and recording a real application workload submitted to a production web application system and includes replay-phase components for replaying the captured application workload against a test web application system in a transactionally consistent manner. The feature provides guarantees about the order of database transactions that are caused when the workload is replayed such that there is a consistency between the replay-phase order of the database transactions and the order of those transactions that occurred when the workload was captured. These consistency guarantees facilitate a faithful reproduction of database changes observed in the production web application system in the test web application system using a captured real application workload. Significantly, this faithful reproduction may be accomplished without having to create a synthetic application workload that approximates or emulates the transactional behavior of the real application workload. Instead, a real application workload may be used as or substantially as it is captured.

Claims

1. A method comprising:

capturing and storing, as a captured application server system workload, a plurality of capture-phase application requests sent to a capture-phase application server system;

assigning an identifier to each capture-phase application request of the plurality of capture-phase application requests;

for at least one capture-phase application request of the plurality of capture-phase application requests, propagating the particular identifier assigned to the at least one capture-phase application request in a capture-phase database request caused by the at least one capture-phase application request, wherein the at least one capture-phase database request comprises a database command;

capturing one or more database sequence numbers assigned to the database command when executed during the capture-phase by a capture-phase database server system against a capture-phase database; and

storing workload data that represents an association between the database command, the one or more database sequence numbers, and the particular identifier assigned to the at least one capture-phase application request;

wherein the method is performed by one or more computing devices.

2. The method of claim 1, wherein capturing the plurality of capture-phase application requests comprises a network sniffer capturing the plurality of capture-phase application requests.

3. The method of claim 1, further comprising:

capturing and storing a plurality of capture-phase application responses sent from the capture-phase application server system in response to the plurality of capture-phase application requests, wherein each capture-phase application response of the plurality of capture-phase application responses comprises the identifier assigned to the capture-phase application request that caused the capture-phase application response to be sent from the production capture-phase application server system.

4. The method of claim 3, further comprising:

for each stored capture-phase application response of the plurality of stored capture-phase application responses,

analyzing the stored capture-phase application response to identify the corresponding identifier included in the stored capture-phase application response, and

modifying the stored capture-phase application request that caused the stored capture-phase application response to include the corresponding identifier such that the stored capture-phase application request, when replayed, will include the corresponding identifier in the replayed request.

5. The method of claim 1, further comprising:

during a replay-phase in which the plurality of capture-phase application requests are being replayed against a replay-phase application server system;

receiving, at a replay-phase database server system, a replay-phase database request comprising the database command and the particular identifier of the at least one capture-phase application request;

based upon the particular identifier of the at least one capture-phase application request and the stored workload data, determining the one or more database sequence numbers that were previously assigned to the database command when previously executed against a capture-phase database during the capture phase;

based upon the one or more database sequence numbers, determining whether to delay execution of the database command against a replay-phase database at least until a particular replay-phase database transaction has been committed to the replay-phase database.

6. The method of claim 5, further comprising:

in response to determining that the particular replay-phase database transaction has not yet been committed to the replay-phase database, delaying execution of the database command against the replay-phase database at least until the particular replay-phase database transaction is committed to the replay-phase database; and

in response to committing the particular replay-phase database transaction to the replay-phase database, executing the database command against the replay-phase database.

7. The method of claim 5, further comprising:

based upon the particular identifier of the at least one capture-phase application request and the stored workload data, determining a database sequence number that was previously assigned to the database command when previously executed against the capture-phase database during the capture-phase that reflects a version of the capture-phase database that the database command was previously executed against during the capture phase.

8. The method of claim 5, further comprising:

based upon the particular identifier of the at least one capture-phase application request and the stored workload data, determining a database sequence number that was previously assigned to the database command when previously executed against the capture-phase database during the application workload capture phase that reflects a version of the capture-phase database that resulted from the previous execution of the database command during the capture phase.

9. The method of claim 5, wherein the replay-phase database server system maintains at least two separate logical locks for tracking changes to the replay-phase database, one logical clock of the at least two logical clocks for tracking all changes to the replay-phase database and the other logical clock of the at least two logical clocks for tracking just changes to the replay-phase database that result from replayed database commands.

10. The method of claim 1, wherein the capture-phase application server system and the replay-phase application server system is the same application server system and/or the capture-phase database server system and the replay-phase database server system is the same database server system.

11. One or more non-transitory computer-readable media having computer-executable instructions recorded thereon for performing a method comprising:

capturing and storing, as a captured application server system workload, a plurality of capture-phase application requests sent to a capture-phase application server system;

assigning an identifier to each capture-phase application request of the plurality of capture-phase application requests;

for at least one capture-phase application request of the plurality of capture-phase application requests, propagating the particular identifier assigned to the at least one capture-phase application request in a capture-phase database request caused by the at least one capture-phase application request, wherein the at least one capture-phase database request comprises a database command;

capturing one or more database sequence numbers assigned to the database command when executed during the capture-phase by a capture-phase database server system against a capture-phase database; and

storing workload data that represents an association between the database command, the one or more database sequence numbers, and the particular identifier assigned to the at least one capture-phase application request.

12. The medium of claim 11, wherein capturing the plurality of capture-phase application requests comprises a network sniffer capturing the plurality of capture-phase application requests.

13. The medium of claim 11, further comprising:

capturing and storing a plurality of capture-phase application responses sent from the capture-phase application server system in response to the plurality of capture-phase application requests, wherein each capture-phase application response of the plurality of capture-phase application responses comprises the identifier assigned to the capture-phase application request that caused the capture-phase application response to be sent from the capture-phase application server system.

14. The medium of claim 13, further comprising:

for each stored capture-phase application response of the plurality of stored capture-phase application responses,

analyzing the stored capture-phase application response to identify the corresponding identifier included in the stored capture-phase application response, and

modifying the stored capture-phase application request that caused the stored capture-phase application response to include the corresponding identifier such that the stored capture-phase application request, when replayed, will include the corresponding identifier in the replayed request.

15. The medium of claim 11, further comprising:

during a replay-phase in which the plurality of capture-phase application requests are being replayed against a replay-phase application server system;

receiving, at a test-replay-phase database server system, a replay-phase database request comprising the database command and the particular identifier of the at least one capture-phase application request;

based upon the particular identifier of the at least one capture-phase application request and the stored workload data, determining the one or more database sequence numbers that were previously assigned to the database command when previously executed against the capture-phase database during the capture phase;

based upon the one or more database sequence numbers, determining whether to delay execution of the database command against a replay-phase database at least until a particular replay-phase database transaction has been committed to the replay-phase database.

16. The medium of claim 15, further comprising:

in response to determining that the particular replay-phase database transaction has not yet been committed to the replay-phase database, delaying execution of the database command against the replay-phase database at least until the particular replay-phase database transaction is committed to the replay-phase database; and

in response to committing the particular replay-phase database transaction to the replay-phase database, executing the database command against the replay-phase database.

17. The medium of claim 15, further comprising:

based upon the particular identifier of the at least one capture-phase application request and the stored workload data, determining a database sequence number that was previously assigned to the database command when previously executed against the capture-phase database during the capture-phase that reflects a version of the capture-phase database that the database command was previously executed against during the capture phase.

18. The medium of claim 15, further comprising:

based upon the particular identifier of the at least one capture-phase application request and the stored workload data, determining a database sequence number that was previously assigned to the database command when previously executed against the capture-phase database during the application workload capture phase that reflects a version of the capture-phase database that resulted from the previous execution of the database command during the capture phase.

19. The medium of claim 15, wherein the replay-phase database server system maintains at least two separate logical locks for tracking changes to the replay-phase database, one logical clock of the at least two logical clocks for tracking all changes to the replay-phase database and the other logical clock of the at least two logical clocks for tracking just changes to the replay-phase database that result from replayed database commands.

20. The medium of claim 11, wherein the capture-phase application server system and the replay-phase application server system is the same application server system and/or the capture-phase database server system and the replay-phase database server system is the same database server system.