EXECUTION OF DATAFLOW JOBS

• US 20110173410A1
• Filed: 01/08/2010
• Published: 07/14/2011
• Est. Priority Date: 01/08/2010
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Spreitzer, Michael J., Whalley, Ian N., Steinder, Malgorzata, Castillo, Claris
• Granted Patent: US 8,539,192 B2
• Time in Patent Office: Days
• US Class Current: 711/170
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3442 for planning or managing the needed capacity
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring

Abstract

A method, system and computer program product for storing data in memory. An example system includes at least one multistage application configured to generate intermediate data in a generating stage of the application and consume the intermediate data in a subsequent consuming stage of the application. A runtime profiler is configured to monitor the application'"'"'s execution and dynamically allocate memory to the application from an in-memory data grid.

Claims

1. A system for storing data in memory:

at least one multistage application configured to generate intermediate data in a generating stage of the application and consume the intermediate data in a subsequent consuming stage of the application;

a runtime profiler configured to monitor the application'"'"'s execution and dynamically allocate memory to the application from an in-memory data grid.

2. The system of claim 1, further comprising:

a plurality of computers, each computer including local volatile memory; and

a grid manager coupling the local volatile memory of each computer to form the in-memory data grid.

3. The system of claim 1, further comprising a pre-profiler configured to generate, prior to execution of the multistage application, an initial profile received by the runtime profiler, the initial profile providing an estimated allocation of memory needed from the in-memory data grid to store intermediate data for the multistage application.

4. The system of claim 3, wherein the initial profile is based, at least in part, on historical data about a size of the intermediate data generated by the multistage application.

5. The system of claim 3, wherein the initial profile is based, at least in part, on input data to the multistage application.

6. The system of claim 3, wherein the initial profile is based, at least in part, on user input indicating an approximate size of the intermediate data generated by the multistage application.

7. A method for storing data in memory:

receiving an estimation of memory required to store intermediate data of a multistage application, the multistage application configured to generate the intermediate data in a generating stage of the application and consume the intermediate data in a subsequent consuming stage of the application;

allocating memory from an in-memory data grid before execution of the multistage application based on the estimation of memory required to store the intermediate data of the multistage application;

executing the multistage application;

monitoring a change in memory required to store the intermediate data during execution of the multistage application; and

adjusting the allocated memory at the in-memory data grid based on the change in memory required to store the intermediate data during execution of the multistage application.

8. The method of claim 7, wherein the estimation of memory required to store the intermediate data of the multistage application is based, at least in part, on historical data about a size of the intermediate data generated by the multistage application.

9. The method of claim 7, wherein the estimation of memory required to store the intermediate data of the multistage application is based, at least in part, on input data to the multistage application.

10. The method of claim 7, wherein the estimation of memory required to store the intermediate data of the multistage application is based, at least in part, on user input indicating an approximate size of the intermediate data generated by the multistage application.

11. The method of claim 7, wherein allocated memory at the in-memory data grid is adjusted to ensure the multistage application has sufficient memory to store the intermediate data at each stage of its execution.

12. The method of claim 7, wherein the in-memory data grid includes a plurality of computers, each computer including local volatile memory, and a grid manager coupling the local volatile memory of each computer to form the in-memory data grid.

13. The method of claim 12, wherein monitoring the change in the memory required to store the intermediate data includes receiving from the grid manager indication of execution progress of the multistage application.

14. A computer program product for storing data in memory, the computer program product comprising:

a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code configured to;

receive an estimation of memory required to store intermediate data of a multistage application, the multistage application configured to generate the intermediate data in a generating stage of the application and consume the intermediate data in a subsequent consuming stage of the application;

allocate memory from an in-memory data grid before execution of the multistage application based on the estimation of memory required to store the intermediate data of the multistage application;

monitor a change in memory required to store the intermediate data during execution of the multistage application; and

adjust the allocated memory at the in-memory data grid based on the change in memory required to store the intermediate data during execution of the multistage application.

15. The computer program product of claim 14, wherein the estimation of memory required to store the intermediate data of the multistage application is based, at least in part, on historical data about a size of the intermediate data generated by the multistage application.

16. The computer program product of claim 14, wherein the estimation of memory required to store the intermediate data of the multistage application is based, at least in part, on input data to the multistage application.

17. The computer program product of claim 14, wherein the estimation of memory required to store the intermediate data of the multistage application is based, at least in part, on user input indicating an approximate size of the intermediate data generated by the multistage application.

18. The computer program product of claim 14, wherein allocated memory at the in-memory data grid is adjusted to ensure the multistage application has sufficient memory to store the intermediate data at each stage of its execution.

19. The computer program product of claim 14, wherein the in-memory data grid includes a plurality of computers, each computer including local volatile memory, and a grid manager coupling the local volatile memory of each computer to form the in-memory data grid.

20. The computer program product of claim 19, wherein the computer readable program code for monitoring the change in the memory required to store the intermediate data includes the computer readable program code for receiving from the grid manager indication of execution progress of the multistage application.