DEPLOYING AN EXECUTABLE WITH HISTORICAL PERFORMANCE DATA

• US 20130198371A1
• Filed: 12/10/2012
• Published: 08/01/2013
• Est. Priority Date: 02/01/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Branson, Michael J., Santosuosso, John M., Schulz, Brandon W.
• Granted Patent: US 9,253,059 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: G06F 2209/508 Monitor
• CPC Class Codes: G06F 9/5044 considering hardware capabilities
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: G06F 9/5088 involving task migration
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters

Abstract

Techniques for incorporating performance data into an executable file for an application are described. Embodiments monitor performance of an application while the application is running. Additionally, historical execution characteristics of the application are determined based upon the monitored performance and one or more system characteristics of a node on which the application was executed on. Embodiments also incorporate the historical execution characteristics into executable file for the application, such that the historical execution characteristics can be used to manage subsequent executions of the application.

Claims

1. A method for incorporating performance data into an executable file for an application, comprising:

monitoring performance of an application while the application is running;

determining historical execution characteristics of the application based on the monitored performance and one or more system characteristics of a node on which the application was executed on; and

incorporating the historical execution characteristics into the executable file for the application, such that the historical execution characteristics can be used to manage subsequent executions of the application.

2. The method of claim 1, wherein the application is a processing element in a stream computing application, and further comprising:

retrieving system information for each of a plurality of nodes;

selecting one or the plurality of nodes to deploy the processing element to based on the retrieved system information and the historical execution characteristics incorporated into the executable file for the processing element; and

deploying the processing element for execution on the selected node.

3. The method of claim 2, wherein the processing element is deployed alongside a plurality of other processing elements, and further comprising:

establishing an operator graph of the plurality of other processing elements and the deployed processing element, the operator graph defining at least one execution path and wherein at least one of the processing elements of the operator graph is configured to receive data from at least one upstream processing element and transmit data to at least one downstream processing element.

4. The method of claim 1, wherein the historical execution characteristics include at least one of processor type, number of processors, amount of memory, type of memory, type of storage, network connectivity characteristics, and system workload.

5. The method of claim 1, further comprising:

determining a number of instances of the application that should be created, based on system information for systems on which the instances of the application will be executed and further based on the execution characteristics; and

creating the determined number of instances of the application on the systems, such that load can be balanced between the created instances of the application.

6. The method of claim 1, further comprising:

deploying the executable file containing the incorporated historical execution characteristics for the application to a first node for execution;

determining whether a potential workload overflow problem exists for the deployed application, based on system information describing attributes of the first node and the historical execution characteristics incorporated into the executable file; and

upon determining a potential workload overflow problem exists, performing a remedial action for the deployed application.

7. The method of claim 6, wherein performing a remedial action includes at least one of (i) spawning a second instance of the application on a second node and discarding the deployed executable file on the first node, (ii) migrating the deployed executable file on the first node to a second node, (iii) modifying an operator graph to reduce a workload of the deployed executable file, and (iv) modifying one or more operations performed by the deployed executable file.

8. The method of claim 6, further comprising:

generating a status notification for the deployed executable file, the status notification indicating a current amount of workload for the executable file and a maximum amount of workload for the executable file, based on current workload information for the first node, the system information describing attributes of the first node and the historical execution characteristics incorporated into the executable file.