TRANSACTION AGGREGATION TO INCREASE TRANSACTION PROCESSING THROUGHOUT

• US 20130007750A1
• Filed: 09/11/2012
• Published: 01/03/2013
• Est. Priority Date: 08/30/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: BECKERLE, Michael James, CARNEY, Michael John
• Granted Patent: US 8,904,393 B2
• Time in Patent Office: Days
• 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:

maintaining a list of aggregated transactions, wherein each of the aggregated transactions includes one or more transaction items, and wherein each of the one or more transaction items has a message identifier and a session identifier;

obtaining a transaction item with a message identifier and a session identifier;

adding the transaction item to an earliest aggregated transaction in an order of the list of aggregated transactions in which no other transaction item has the same session identifier;

executing an aggregated transaction in the list of aggregated transactions that has met execution criteria;

in response to determining that the aggregated transaction is not committing,

breaking up the aggregated transaction into multiple smaller aggregated transactions; and

adjusting a target size of each of the multiple smaller aggregated transactions based on measurements of system throughput.

2. The method of claim 1, further comprising:

in response to the adjusting, placing the multiple smaller aggregated transactions on front of the list of aggregated transactions; and

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

3. 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 a predetermined target size.

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

detecting one or more errors;

for each of the one or more errors, extracting a message identifier that is associated with a transaction item that caused that error; and

breaking up the aggregated transaction into the multiple smaller aggregated transactions such that each of the multiple smaller aggregated transactions contains at most one transaction item that caused an error.

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

determining that error causes are not available; and

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

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

7. The method of claim 1, further comprising:

before adding transaction items to the aggregated transactions in 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.

8. The method of claim 1, further comprising:

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

9. The method of claim 1, further comprising:

in response to determining that the aggregated transaction has committed, adjusting the target size of each aggregated transaction based on measurements of system throughput.

10. A computer program product comprising a storage device storing a computer readable program, wherein the computer readable program when executed by a processor on a computer causes the computer to:

maintain a list of aggregated transactions, wherein each of the aggregated transactions includes one or more transaction items, and wherein each of the one or more transaction items has a message identifier and a session identifier;

obtain a transaction item with a message identifier and a session identifier;

add the transaction item to an earliest aggregated transaction in an order of the list of aggregated transactions in which no other transaction item has the same session identifier;

execute an aggregated transaction in the list of aggregated transactions that has met execution criteria;

in response to determining that the aggregated transaction is not committing,

break up the aggregated transaction into multiple smaller aggregated transactions; and

adjust a target size of each of the multiple smaller aggregated transactions based on measurements of system throughput.

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

in response to the adjusting, place the multiple smaller aggregated transactions on front of the list of aggregated transactions; and

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

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

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

detect one or more errors;

for each of the one or more errors, extract a message identifier that is associated with a transaction item that caused that error; and

break up the aggregated transaction into the multiple smaller aggregated transactions such that each of the multiple smaller aggregated transactions contains at most one transaction item that caused an error.

14. The computer program product of claim 10, 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; and

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

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

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

before adding transaction items to the aggregated transactions in 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.

17. The computer program product of claim 10, 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.

18. The computer program product of claim 10, 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 of each aggregated transaction based on measurements of system throughput.

19. A system, comprising:

logic capable of performing operations, the operations comprising;

maintaining a list of aggregated transactions, wherein each of the aggregated transactions includes one or more transaction items, and wherein each of the one or more transaction items has a message identifier and a session identifier;

obtaining a transaction item with a message identifier and a session identifier;

adding the transaction item to an earliest aggregated transaction in an order of the list of aggregated transactions in which no other transaction item has the same session identifier;

executing an aggregated transaction in the list of aggregated transactions that has met execution criteria;

in response to determining that the aggregated transaction is not committing,

breaking up the aggregated transaction into multiple smaller aggregated transactions; and

adjusting a target size of each of the multiple smaller aggregated transactions based on measurements of system throughput.

20. The system of claim 19, wherein the operations further comprise:

in response to the adjusting, placing the multiple smaller aggregated transactions on front of the list of aggregated transactions; and

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

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

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

detecting one or more errors;

for each of the one or more errors, extracting a message identifier that is associated with a transaction item that caused that error; and

breaking up the aggregated transaction into the multiple smaller aggregated transactions such that each of the multiple smaller aggregated transactions contains at most one transaction item that caused an error.

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

determining that error causes are not available; and

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

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

25. The system of claim 19, wherein the operations further comprise:

before adding transaction items to the aggregated transactions in 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.

26. The system of claim 19, wherein the operations further comprise:

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

27. The system of claim 19, wherein the operations further comprise:

in response to determining that the aggregated transaction has committed, adjusting the target size of each aggregated transaction based on measurements of system throughput.