# US 2013/0254754 A1 · Methods and systems for optimizing the performance of software applications at runtime

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0254754 A1
- Document ID: US20130254754A1
- Status: Published application
- Kind: A1
- Application number: 13/532,490
- Filed: 2012-06-25
- Published: 2013-09-26
- Earliest claimed: 2012-03-20
- Assignees: Infosys Limited
- Inventors: Prasanna RAJARAMAN
- Web page: https://patentgrep.com/patent/US20130254754A1

## CPC

- G06F 8/456: {Parallelism detection}
- G06F 11/3404: {for parallel or distributed programming}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and method for optimizing the performance of software applications are described. Embodiments include computer implemented steps for identifying at least two constituent software components for parallel execution, executing the identified software components, profiling the performance of the one or more software components at an execution time, creating an optimization model with the set of data gathered from profiling the execution of the one or more software components, and marking at least two software components for execution in parallel in a subsequent execution on the basis of the optimization model. In additional embodiments, the optimization model may be reconfigured on the basis of a cost-benefit analysis of parallelization, and the software components involved marked for sequential execution if the resource overhead associated with parallelization exceeds the corresponding resource or throughput benefit.

## Claims

### Claim 1

A computer implemented method for optimizing the performance of one or more software components, the method comprising:
identifying at least two constituent software components for parallel execution, wherein the software components comprise a software application, workflow, process, or a software component implementing at least one discrete functionality;
executing the identified software components;
profiling the performance of the one or more software components at an execution time, wherein profiling comprises gathering a set of data related to one or more performance characteristics of the one or more software components at runtime;
creating an optimization model with the set of data gathered from profiling the execution of the one or more software components, wherein criteria involved in the design of the optimization model comprises a resource requirement for executing a software component or a cost-benefit evaluation associated with an overhead involved in the execution of a software component in parallel with other identified software components; and
marking at least two software components for execution in parallel in a subsequent execution on the basis of the optimization model.

### Claim 2 (depends on 1)

The computer implemented method as claimed in claim 1, wherein identifying is performed at a design time by a developer.

### Claim 3 (depends on 1)

The computer implemented method as claimed in claim 1, wherein identifying is performed by the compiler at a compile time.

### Claim 4 (depends on 1)

The computer implemented method as claimed in claim 1, wherein identifying is performed at an execution runtime based on a predefined algorithm.

### Claim 5 (depends on 4)

The computer implemented method as claimed in claim 4, wherein the runtime comprises an operating system, a virtual machine, or an application server which controls the execution of the software components.

### Claim 6 (depends on 1)

The computer implemented method as claimed in claim 1, wherein identifying comprises marking, by a user, at least two software components for parallel execution.

### Claim 7 (depends on 1)

The computer implemented method as claimed in claim 1, wherein identifying comprises marking, by a computer, at least two software components for parallel execution.

### Claim 8 (depends on 1)

The computer implemented method as claimed in claim 1, wherein the set of data gathered by profiling comprises a processor utilization metric, a memory usage metric, a disk usage metric, a network usage metric or a computational resource overhead involved in running components parallelly.

### Claim 9 (depends on 1)

The computer implemented method as claimed in claim 1, further comprising profiling the performance and resource requirement of the one or more software components in each execution thereof

### Claim 10 (depends on 9)

The computer implemented method as claimed in claim 9, further comprising refining the optimization model following each iteration on the basis of the set of data gathered by profiling the performance of the one or more software components.

### Claim 11 (depends on 10)

The computer implemented method as claimed in claim 10, wherein the overhead associated with the execution of each of the one or more software components is determinative of the optimization model.

### Claim 12 (depends on 10)

The computer implemented method as claimed in claim 10, wherein the one or more marked software components are marked for sequential execution if a resource associated with the execution of at least two of the marked software components in parallel exceeds available runtime resources.

### Claim 13 (depends on 10)

The computer implemented method as claimed in claim 10, wherein one or more marked software components are marked for sequential execution if throughput of the system for execution of the one or more software components is negatively affected by the execution of at least two of the one or more software components in parallel.

### Claim 14

A system for optimizing the performance of one or more software components, the system comprising:
one or more processing units; and
a processor readable memory, the memory containing one or more programming instructions to:
identify at least two constituent software components for parallel execution, wherein the software components comprise a software application, a workflow, a process, or a software component implementing one or more discrete functionality;
execute the identified software components;
profile the performance of the one or more software components at an execution time, wherein profiling comprises gathering a set of data related to one or more performance characteristics of the one or more software components at runtime;
create an optimization model with the set of data gathered from profiling the execution of the one or more software components; and
mark at least two software components for execution in parallel in a subsequent execution on the basis of the optimization model.

### Claim 15 (depends on 14)

The system as claimed in claim 14, wherein identifying is performed at a design time by a developer.

### Claim 16 (depends on 14)

The system as claimed in claim 14, wherein identifying is performed by the compiler at a constuction time.

### Claim 17 (depends on 14)

The system as claimed in claim 14, wherein identifying is performed at an execution runtime based on a predefined algorithm.

### Claim 18 (depends on 17)

The system as claimed in claim 17, wherein the runtime environment comprises an operating system, a virtual machine, or an application server which controls the execution of the software components.

### Claim 19 (depends on 14)

The system as claimed in claim 14, wherein identifying comprises marking, by a user, at least two software components for parallel execution.

### Claim 20 (depends on 14)

The system as claimed in claim 14, wherein identifying comprises marking, by a system, at least two software components for parallel execution.

### Claim 21 (depends on 14)

The system as claimed in claim 14, wherein the set of data gathered by profiling comprises a processor utilization metric, a memory usage metric, a disk usage metric, a network usage metric or a computational resource overhead involved in running the software components in parallel.

### Claim 22 (depends on 14)

The system as claimed in claim 14, wherein the one or more software components are executed sequentially.

### Claim 23 (depends on 22)

The system as claimed in claim 22, further comprising profiling the performance and resource requirement of the one or more software components in each execution thereof.

### Claim 24 (depends on 23)

The system as claimed in claim 23, further comprising refining the optimization model following each iteration on the basis of the set of data gathered by profiling the performance of the one or more software components.

### Claim 25 (depends on 24)

The system as claimed in claim 24, wherein the resource overhead associated with the execution of each of the one or more software components is determinative of the optimization model.

### Claim 26 (depends on 23)

The system as claimed in claim 23, wherein the one or more marked software components are marked for sequential execution if a resource overhead associated with the execution of at least two of the marked software components in parallel exceeds available runtime resources.

### Claim 27 (depends on 23)

The system as claimed in claim 23, wherein one or more marked software components are marked for sequential execution if throughput of the system for execution of the one or more software components is negatively affected by the execution of at least two of the one or more software components in parallel.

### Claim 28

A non-transitory computer readable storage medium having stored thereon computer executable instructions for performing a method of optimizing the performance of one or more software components at runtime, the method comprising:
identifying at least two constituent software components for parallel execution, wherein the software components comprise a software application, a workflow, a process, or a software component implementing at least one discrete functionality;
executing the identified software components;
profiling the performance of the one or more software components at an execution time, wherein profiling comprises gathering a set of data related to one or more performance characteristics of the one or more software components at runtime, and wherein the set of data gathered by profiling comprises a processor utilization metric, a memory usage metric, a disk usage metric or a computational resource overhead involved in running components parallelly;
creating an optimization model with the set of data gathered from profiling the execution of the one or more software components, wherein criteria involved in the design of the optimization model comprise resource availability or a cost-benefit evaluation associated with an overhead involved in the execution of a component in parallel with other identified components; and
marking at least two software components for execution in parallel in a subsequent execution on the basis of the optimization model.
