# US 2025/0094183 A1 · Performance optimizations for data operations

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

- Number: US 2025/0094183 A1
- Document ID: US20250094183A1
- Status: Published application
- Kind: A1
- Application number: 18/469,690
- Filed: 2023-09-19
- Published: 2025-03-20
- Earliest claimed: 2023-09-19
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Alexander OCHER; Sreenivasulu GELLE; Manali PISE
- Web page: https://patentgrep.com/patent/US20250094183A1

## CPC

- G06F 9/448: Execution paradigms, e.g. implementations of programming paradigms
- G06F 16/24561: {Intermediate data storage techniques for performance improvement}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Embodiments may be associated with a data source and a data service tool. A performance optimizer may determine a new type of data job to be executed based on a job execution parameter, perform a first execution of the new type of data job (such that data operations are performed at the data service tool), and collect first performance results. The performance optimizer then performs a second execution of the new type of data job (such that data operations are pushed down and performed at the data source) and collects second performance results. The first and second performance results are compared, and a result storage is updated with an indication of whether subsequent executions of the new type of data job will perform data operations at the data service tool or at the data source. The indication stored in the result storage may comprise, for example, a pushdown flag.

## Claims

### Claim 1

A system, comprising:
a data source;
a data service tool;
a result storage; and
a performance optimizer coupled to the data source, the data service tool, and the result storage, including:
a computer processor, and
a computer memory coupled to the computer processor and storing instructions that, when executed by the computer processor, cause the performance optimizer to:
determine a new type of data job to be executed based on a job execution parameter,
perform a first execution of the new type of data job, such that data operations are performed at the data service tool, and collect first performance results,
perform a second execution of the new type of data job, such that data operations are pushed down and performed at the data source, and collect second performance results,
compare the first and second performance results, and
update the result storage with an indication of whether subsequent executions of the new type of data job will perform data operations at the data service tool or at the data source.

### Claim 2 (depends on 1)

The system of claim 1, wherein the data source is associated with at least one of: (i) a database, and (ii) a database-based application.

### Claim 3 (depends on 1)

The system of claim 1, wherein the data service tool is associated with a special table object that contains data from several different database tables.

### Claim 4 (depends on 1)

The system of claim 1, wherein the data operations are associated with at least one of: (i) a sort, (ii) a search, (iii) a replace, (iv) an arithmetic operation, and (v) a data join.

### Claim 5 (depends on 1)

The system of claim 1, wherein the first and second performance results are associated with at least one of: (i) an execution time, (ii) Central Processing Unit (“CPU”) usage, (iii) memory utilization, and (iv) an Input Output (“IO”) parameter.

### Claim 6 (depends on 1)

The system of claim 1, wherein the indication stored in the result storage comprises a pushdown flag.

### Claim 7 (depends on 6)

The system of claim 6, wherein the result storage is accessed prior to execution of a subsequent data job and the data operations are performed in accordance with the appropriate pushdown flag.

### Claim 8 (depends on 7)

The system of claim 7, wherein the appropriate pushdown flag is based at least in part on: (i) the type of data job, (ii) a particular data source, (iii) a particular data service tool, and (iv) a type of information being accessed.

### Claim 9

A method, comprising:
determining, by a computer processor of a performance optimizer, a new type of data job to be executed, based on a job execution parameter, in connection with a data source and a data service tool;
performing a first execution of the new type of data job, such that data operations are performed at the data service tool, and collecting first performance results;
performing a second execution of the new type of data job, such that data operations are pushed down and performed at the data source, and collecting second performance results;
comparing the first and second performance results; and
updating a result storage with an indication of whether subsequent executions of the new type of data job will perform data operations at the data service tool or at the data source.

### Claim 10 (depends on 9)

The method of claim 9, wherein the data source is associated with at least one of: (i) a database, and (ii) a database-based application.

### Claim 11 (depends on 9)

The method of claim 9, wherein the data service tool is associated with a special table object that contains data from several different database tables.

### Claim 12 (depends on 9)

The method of claim 9, wherein the data operations are associated with at least one of: (i) a sort, (ii) a search, (iii) a replace, (iv) an arithmetic operation, and (v) a data join.

### Claim 13 (depends on 9)

The method of claim 9, wherein the first and second performance results are associated with at least one of: (i) an execution time, (ii) Central Processing Unit (“CPU”) usage, (iii) memory utilization, and (iv) an Input Output (“IO”) parameter.

### Claim 14 (depends on 9)

The method of claim 9, wherein the indication stored in the result storage comprises a pushdown flag.

### Claim 15 (depends on 9)

The method of claim 9, wherein the result storage is accessed prior to execution of a subsequent data job and the data operations are performed in accordance with the appropriate pushdown flag.

### Claim 16 (depends on 7)

The method of claim 7, wherein the appropriate pushdown flag is based at least in part on: (i) the type of data job, (ii) a particular data source, (iii) a particular data service tool, and (iv) a type of information being accessed.

### Claim 17

A non-transitory, machine-readable medium comprising instructions thereon that, when executed by a processor, cause the processor to execute operations to perform a method, the method comprising:
determining, by a computer processor of a performance optimizer, a new type of data job to be executed, based on a job execution parameter, in connection with a data source and a data service tool;
performing a first execution of the new type of data job, such that data operations are performed at the data service tool, and collecting first performance results;
performing a second execution of the new type of data job, such that data operations are pushed down and performed at the data source, and collecting second performance results;
comparing the first and second performance results; and
updating a result storage with an indication of whether subsequent executions of the new type of data job will perform data operations at the data service tool or at the data source.

### Claim 18 (depends on 17)

The medium of claim 17, wherein the data source is associated with at least one of: (i) a database, and (ii) a database-based application.

### Claim 19 (depends on 17)

The medium of claim 17, wherein the data service tool is associated with a special table object that contains data from several different database tables.

### Claim 20 (depends on 17)

The medium of claim 17, wherein the data operations are associated with at least one of: (i) a sort, (ii) a search, (iii) a replace, (iv) an arithmetic operation, and (v) a data join.

### Claim 21 (depends on 17)

The medium of claim 17, wherein the first and second performance results are associated with at least one of: (i) an execution time, (ii) Central Processing Unit (“CPU”) usage, (iii) memory utilization, and (iv) an Input Output (“IO”) parameter.
