# US 2025/0086015 A1 · Apparatus and a method and a non-transitory machine-readable storage medium

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

- Number: US 2025/0086015 A1
- Document ID: US20250086015A1
- Status: Published application
- Kind: A1
- Application number: 18/890,806
- Filed: 2024-09-20
- Published: 2025-03-13
- Earliest claimed: 2023-09-20
- Inventors: Antonio VALLES; Rebecca DAVID
- Web page: https://patentgrep.com/patent/US20250086015A1

## CPC

- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 2201/865: Monitoring of software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

It is provided an apparatus comprising interface circuitry, machine-readable instructions, and processing circuitry to execute the machine-readable instructions. The machine-readable instructions include instructions to: obtain execution phases of an application; to determine critical execution phases among the obtained execution phases based on one or more execution-performance metrics of the execution phases; to cluster execution tasks performed in the determined critical execution phases into one or more clusters corresponding to the respective execution phase based on a runtime behavior of the respective execution tasks; and to generate a performance model based on the determined clusters. The execution phases are designated during a first execution of the application. The execution of the application comprising a plurality of parallel-executing processes distributed on a single node or across a plurality of nodes. The execution phases are determined based on communication events among at least a part of the plurality of processes.

## Claims

### Claim 1

An apparatus comprising interface circuitry, machine-readable instructions and processing circuitry to execute the machine-readable instructions to:
obtain execution phases of an application, the execution phases being designated during a first execution of the application, the execution of the application comprising a plurality of parallel-executing processes on a single node or distributed across a plurality of nodes,
wherein the execution phases are determined based on communication events among at least a part of the plurality of processes;
determine critical execution phases among the obtained execution phases based on one or more execution-performance metrics of the execution phases;
cluster execution tasks performed in the determined critical execution phases into one or more clusters corresponding to the respective execution phase based on a runtime behavior of the respective execution tasks;
generate a performance model based on the determined clusters.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the processing circuitry is further to execute the machine-readable instructions to analyze an execution of the application based on the generated performance model.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the processing circuitry is further to execute the machine-readable instructions to optimize an execution of the application based on the generated performance model.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the clustering is performed by a clustering algorithm into a number of clusters for each of the critical execution phases.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the processing circuitry is further to execute the machine-readable instructions to determine a cluster average for each of the determined clusters with regards to the runtime behavior used for clustering.

### Claim 6 (depends on 5)

The apparatus of claim 5, wherein the processing circuitry is further to execute the machine-readable instructions to determine a representative execution task for each of the determined clusters, wherein the representative execution task is the respective execution task that is closest to the respective determined cluster average.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein the processing circuitry is further to execute the machine-readable instructions to generate the performance model based on the determined representative execution task for each of the determined clusters and the corresponding number of times execution task of the respective cluster executed.

### Claim 8 (depends on 7)

The apparatus of claim 7, wherein the processing circuitry is further to execute the machine-readable instructions to analyze the determined representative execution task for each of the determined clusters with regards to the one or more execution-performance metrics during a second execution of the application.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the one or more execution performance metrics comprise at least one of the following: resource utilization, communication overhead, critical computational tasks, I/O intensity, thread utilization, number or names of GPU or CPU or driver function calls, hardware events and call stack behavior.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the processing circuitry is further to execute the machine-readable instructions to capture application data during the execution phases of the first and/or second execution of the application; and
determine the runtime behavior of the respective execution tasks based on the captured application data.

### Claim 11 (depends on 1)

The apparatus of claim 1, wherein the runtime behavior of a respective execution task comprises at least one of a: duration of the respective execution task, retired instructions of the respective execution task, hardware events of the respective execution task.

### Claim 12 (depends on 1)

The apparatus of claim 1, wherein an execution phase is starting at the end of a first communication event and is ending at the end of the consecutive communication event.

### Claim 13 (depends on 1)

The apparatus of claim 1, wherein the execution phases are determined based on Messaging Passing Interface, MPI, communication events among the plurality of processes.

### Claim 14 (depends on 1)

The apparatus of claim 1, wherein an execution phase is starting at end of a Messaging Passing Interface, MPI, collective communication event and is ending at the end of the consecutive MPI collective communication event.

### Claim 15 (depends on 1)

The apparatus of claim 1, wherein the execution phases are determined based on two consecutive Messaging Passing Interface, MPI, communication events among the plurality of processes.

### Claim 16 (depends on 1)

The apparatus of claim 1, wherein the MPI collective communication event is at least one of the following: broadcasting, reducing, all-reducing, synchronizing, and gathering.

### Claim 17

A method comprising:
obtaining execution phases of an application, the execution phases being designated during a first execution of the application, the execution of the application comprising a plurality of parallel-executing processes on a single node or distributed across a plurality of nodes,
wherein the execution phases are determined based on communication events among at least a part of the plurality of processes;
determining critical execution phases among the obtained execution phases based on one or more execution-performance metrics of the execution phases;
clustering execution tasks performed in the determined critical execution phases into one or more clusters corresponding to the respective execution phase based on a runtime behavior of the respective execution tasks;
generating a performance model based on the determined clusters.

### Claim 18 (depends on 17)

The method of claim 17, further comprising analyzing an execution of the application based on the generated performance model.

### Claim 19 (depends on 17)

The method of claim 17, further comprising optimizing an execution of the application based on the generated performance model.

### Claim 20 (depends on 17)

A non-transitory machine-readable storage medium including program code, when executed, to cause a machine to perform the method of claim 17.
