Transaction aggregation to increase transaction processing throughput

• US 8,904,393 B2
• Filed: 09/11/2012
• Issued: 12/02/2014
• Est. Priority Date: 08/30/2007
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Beckerle, Michael James, Carney, Michael John
• Primary Examiner(s): Kawsar, Abdullah Al
• Assistant Examiner(s): Rashid, Wissam
• Application Number:
  US13/610,668
• Publication Number:
  US 20130007750A1
• Time in Patent Office: 812 Days
• Field of Search: None
• US Class Current: 718/101
• CPC Class Codes: G06F 2209/5017 Task decomposition
• CPC Class Codes: G06F 2209/506 Constraint
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/5038 considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration scheduling strategies G06F9/4881 and subgroups

Abstract

Provided are techniques for increasing transaction processing throughput. A transaction item with a message identifier and a session identifier is obtained. The transaction item is added to an earliest aggregated transaction in a list of aggregated transactions in which no other transaction item as the same session identifier. A first aggregated transaction in the list of aggregated transactions that has met execution criteria is executed. In response to determining that the aggregated transaction is not committing, the aggregated transaction is broken up into multiple smaller aggregated transactions and a target size of each aggregated transaction is adjusted based on measurements of system throughput.

Claims

1. A computer-implemented method, comprising:

in response to an aggregated transaction on a list of aggregated transactions reaching a target size that represents execution criteria, executing the aggregated transaction, wherein the aggregated transaction includes transaction items; and

in response to determining that errors occurred to prevent the aggregated transaction from committing,

breaking up the aggregated transaction into multiple, smaller aggregated transactions that each include one transaction item that caused an error from the errors that occurred and at least one transaction item that did not cause an error from the errors that occurred;

placing the multiple, smaller aggregated transactions on a front of a list of aggregated transactions to be executed;

labeling the multiple, smaller aggregated transactions as already having met the execution criteria;

adjusting the target size for determining whether aggregated transactions on the list of aggregated transactions, other than the multiple, smaller, aggregated transactions, have met execution criteria based on measurements of system throughput; and

in response to determining that one of the multiple, smaller aggregated transactions has met the execution criteria based on the labelling, executing that one of the multiple, smaller aggregated transactions.

2. The method of claim 1, wherein the execution criteria comprises at least one of expiration of a timer and a size of the aggregated transaction reaching the target size.

3. The method of claim 1, wherein breaking up the aggregated transaction further comprises:

for each of the errors that occurred, extracting a message identifier that is associated with a transaction item that caused that error.

4. The method of claim 1, wherein breaking up the aggregated transaction further comprises:

determining that error causes are not available for the errors that occurred; and

in response to determining that the error causes are not available, breaking up the aggregated transaction into other, multiple, smaller aggregated transactions.

5. The method of claim 1, wherein executing the aggregated transaction comprises sending the aggregated transaction down a dataflow execution process.

6. The method of claim 1, further comprising:

before adding transaction items to the aggregated transactions on the list of aggregated transactions, dividing up incoming transaction items into partitions, wherein transaction items having a same session identifier are in a same partition.

7. The method of claim 1, further comprising:

pipelining individual transaction items making up the aggregated transaction into a dataflow execution process.

8. The method of claim 1, further comprising:

in response to determining that the aggregated transaction has committed, adjusting the target size for determining whether another aggregated transaction on the list of aggregated transactions has met the execution criteria based on the measurements of the system throughput.

9. A computer program product comprising a non-transitory computer readable storage medium storing a computer readable program, wherein the computer readable program when executed by a processor on a computer causes the computer to:

in response to an aggregated transaction on a list of aggregated transactions reaching a target size that represents execution criteria, execute the aggregated transaction, wherein the aggregated transaction includes transaction items; and

in response to determining that errors occurred to prevent the aggregated transaction from committing,

break up the aggregated transaction into multiple, smaller aggregated transactions that each include one transaction item that caused an error from the errors that occurred and at least one transaction item that did not cause an error from the errors that occurred; and

place the multiple, smaller aggregated transactions on a front of a list of aggregated transactions to be executed;

label the multiple, smaller aggregated transactions as already having met the execution criteria;

adjust the target size for determining whether aggregated transactions on the list of aggregated transactions, other than the multiple, smaller, aggregated transactions, have met execution criteria based on measurements of system throughput; and

in response to determining that one of the multiple, smaller aggregated transactions has met the execution criteria based on the labelling, execute that one of the multiple, smaller aggregated transactions.

10. The computer program product of claim 9, wherein the execution criteria comprises at least one of expiration of a timer and a size of the aggregated transaction reaching the target size.

11. The computer program product of claim 9, wherein when breaking up the aggregated transaction, the computer readable program when executed on a computer causes the computer to:

for each of the errors that occurred, extract a message identifier that is associated with a transaction item that caused that error.

12. The computer program product of claim 9, wherein when breaking up the aggregated transaction, the computer readable program when executed on a computer causes the computer to:

determine that error causes are not available for the errors that occurred; and

in response to determining that the error causes are not available, break up the aggregated transaction into other, multiple, smaller aggregated transactions.

13. The computer program product of claim 9, wherein executing the aggregated transaction comprises sending the aggregated transaction down a dataflow execution process.

14. The computer program product of claim 9, wherein the computer readable program when executed on a computer causes the computer to:

before adding transaction items to the aggregated transactions on the list of aggregated transactions, divide up incoming transaction items into partitions, wherein transaction items having a same session identifier are in a same partition.

15. The computer program product of claim 9, wherein the computer readable program when executed on a computer causes the computer to:

pipeline individual transaction items making up the aggregated transaction into a dataflow execution process.

16. The computer program product of claim 9, wherein the computer readable program when executed on a computer causes the computer to:

in response to determining that the aggregated transaction has committed, adjust the target size for determining whether another aggregated transaction on the list of aggregated transactions has met the execution criteria based on the measurements of the system throughput.

17. A system, comprising:

a processor;

a storage device coupled to the processor, wherein the storage device stores program code, and wherein the processor executes the program code to perform operations, the operations comprising;

in response to an aggregated transaction on a list of aggregated transactions reaching a target size that represents execution criteria, executing the aggregated transaction, wherein the aggregated transaction includes transaction items; and

in response to determining that errors occurred to prevent the aggregated transaction from committing,

breaking up the aggregated transaction into multiple, smaller aggregated transactions that each include one transaction item that caused an error from the errors that occurred and at least one transaction item that did not cause an error from the errors that occurred;

placing the multiple, smaller aggregated transactions on a front of a list of aggregated transactions to be executed;

labeling the multiple, smaller aggregated transactions as already having met the execution criteria;

adjusting the target size for determining whether aggregated transactions on the list of aggregated transactions, other than the multiple, smaller, aggregated transactions, have met execution criteria based on measurements of system throughput; and

in response to determining that one of the multiple, smaller aggregated transactions has met the execution criteria based on the labelling, executing that one of the multiple, smaller aggregated transactions.

18. The system of claim 17, wherein the execution criteria comprises at least one of expiration of a timer and a size of the aggregated transaction reaching the target size.

19. The system of claim 17, wherein operations for breaking up the aggregated transaction further comprise:

for each of the errors that occurred, extracting a message identifier that is associated with a transaction item that caused that error.

20. The system of claim 17, wherein operations for breaking up the aggregated transaction further comprise:

determining that error causes are not available for the errors that occurred; and

in response to determining that the error causes are not available, breaking up the aggregated transaction into other, multiple, smaller aggregated transactions.

21. The system of claim 17, wherein executing the aggregated transaction comprises sending the aggregated transaction down a dataflow execution process.

22. The system of claim 17, wherein the operations further comprise:

before adding transaction items to the aggregated transactions on the list of aggregated transactions, dividing up incoming transaction items into partitions, wherein transaction items having a same session identifier are in a same partition.

23. The system of claim 17, wherein the operations further comprise:

pipelining individual transaction items making up the aggregated transaction into a dataflow execution process.

24. The system of claim 17, wherein the operations further comprise:

in response to determining that the aggregated transaction has committed, adjusting the target size for determining whether another aggregated transaction on the list of aggregated transactions has met the execution criteria based on the measurements of the system throughput.