# US 2025/0094224 A1 · Memory-tracking resource manager for elastic distributed graph-processing system

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

- Number: US 2025/0094224 A1
- Document ID: US20250094224A1
- Status: Published application
- Kind: A1
- Application number: 18/369,254
- Filed: 2023-09-18
- Published: 2025-03-20
- Earliest claimed: 2023-09-18
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Calin Iorgulescu; Martin Kucera; Vasileios Trigonakis; Arnaud Delamare; Petr Koupy; Jinsu Lee; Sungpack Hong; Hassan Chafi
- Web page: https://patentgrep.com/patent/US20250094224A1

## CPC

- G06F 9/5016: {the resource being the memory}
- G06F 9/485: {Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence)}
- G06F 2209/5014: Reservation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A resource manager tracks the amount of available memory for a cluster of machines and for each machine in the cluster. The resource manager receives a reservation request from a job for a graph processing operation. The reservation request specifies an identification of the job, a type of reservation, and an amount of memory requested. The resource manager determines whether to grant the reservation request based on the type of reservation, the amount of memory requested, and the amount of available memory in the cluster or in one or more machines in the cluster. In response to determining to grant the reservation request, the resource manager sends a response to the job indicating an amount of memory reserved and adjusts the amount of available cluster memory and the amount of available machine memory for at least one machine in the cluster based on the amount of memory reserved.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving, by a resource manager, a reservation request from a job for a graph processing operation, wherein:
the resource manager tracks an amount of available cluster memory for a cluster of machines and an amount of available machine memory in each machine in the cluster, and
the reservation request specifies an identification of the job, a type of reservation, and an amount of memory requested;
determining, by the resource manager, whether to grant the reservation request based on the type of reservation, the amount of memory requested, and the amount of available cluster memory or the amount of available machine memory in one or more machines in the cluster; and
in response to the resource manager determining to grant the reservation request:
sending a response to the job indicating an amount of memory reserved; and
adjusting the amount of available cluster memory and the amount of available machine memory for at least one machine in the cluster based on the amount of memory reserved,
wherein the method is performed by one or more computing devices.

### Claim 2 (depends on 1)

The method of claim 1, wherein:
the type of reservation is selected from the group consisting of pre-reservation, flexible reservation, or fixed reservation,
the pre-reservation type requests a guarantee that the amount of memory requested is available in the cluster,
the flexible reservation type requests a guarantee that the amount of memory requested is available in the cluster and a guarantee that the amount of memory requested is available in a specified machine within the cluster,
the fixed reservation type requests a guarantee that the amount of memory requested is available in the cluster, a guarantee that the amount of memory requested is available in a specified machine within the cluster, and a guarantee that the amount of memory requested will reside on the specified machine if the job is restarted, and
memory reserved for a reservation request of a pre-reservation type is subsequently bound to one or more machines using one or more subsequent reservation requests of flexible reservation or fixed reservation types.

### Claim 3 (depends on 1)

The method of claim 1, wherein physical memory is allocated to the job without involvement of the resource manager.

### Claim 4 (depends on 1)

The method of claim 1, wherein the resource manager reserves memory based on a predetermined increment to cover the amount of memory requested.

### Claim 5 (depends on 4)

The method of claim 4, wherein the resource manager uses a configurable function to determine the amount of memory reserved for the reservation request in response to determining the job was previously put on hold from an implicit reservation.

### Claim 6 (depends on 5)

The method of claim 5, wherein the configurable function comprises applying an exponential factor function to the predetermined increment.

### Claim 7 (depends on 1)

The method of claim 1, wherein:
the job commits persistent objects in persistent object memory,
adjusting the amount of available cluster memory and the amount of available machine memory comprises:
determining the amount of available cluster memory as an amount of physical cluster memory minus an amount of memory reserved for all jobs currently executing in the cluster minus an amount of persistent object memory in the cluster; and
determining the amount of available machine memory for a given machine as an amount of physical machine memory for the given machine minus an amount of memory reserved for all jobs currently executing in the given machine minus an amount of persistent object memory in the given machine.

### Claim 8 (depends on 1)

The method of claim 1, wherein the resource manager is a centralized resource manager servicing reservation requests from all jobs executing within the cluster.

### Claim 9 (depends on 1)

The method of claim 1, wherein:
the resource manager is a decentralized resource manager comprising a plurality of resource manager instances running on respective machines in the cluster, and
each resource manager instance within the plurality of resource manager instances propagates changes to the amount of available cluster memory and the amount of available machine memory in each machine in the cluster to other resource manager instances in the plurality of resource manager instances using a replication protocol.

### Claim 10 (depends on 1)

The method of claim 1, wherein:
the job executes the graph processing operation in a graph runtime system, and
the resource manager is external to the graph runtime system.

### Claim 11 (depends on 1)

The method of claim 1, wherein:
the job comprises a plurality of processes,
the resource manager receives the reservation request from a particular process within the plurality of processes, and
the method further comprises:
in response to the resource manager determining to deny the reservation request, sending a response to the particular process indicating a denial of the reservation request and putting the plurality of processes on hold.

### Claim 12 (depends on 1)

The method of claim 1, further comprising:
in response to the resource manager determining to deny the reservation request, sending a response to job indicating a denial of the reservation request,
wherein the job is put on hold and restarts in response to receiving the response indicating denial of the reservation request.

### Claim 13 (depends on 1)

The method of claim 1, further comprising:
in response to the resource manager determining to deny the reservation request, sending a response to job indicating a denial of the reservation request,
wherein the job saves an intermediate state in response to receiving the response indicating denial of the reservation request and resumes execution in response to the amount of memory requested becoming available.

### Claim 14 (depends on 1)

The method of claim 1, further comprising:
receiving, by the resource manager from the job, a reservation trim request to trim an amount of memory reserved for the job; and
adjusting the amount of available cluster memory and the amount of available machine memory for at least one machine in the cluster based on the amount of memory specified in the reservation trim request.

### Claim 15 (depends on 1)

The method of claim 1, wherein:
the job has a user-defined memory limit, and
the resource manager determines to deny the reservation request in response to determining the job has exceeded its user-defined memory limit.

### Claim 16 (depends on 1)

The method of claim 1, wherein the job either destroys or commits graph data objects in memory at an end of job execution.

### Claim 17 (depends on 1)

The method of claim 1, further comprising:
in response to detecting an unfairness condition, automatically reverting to a pessimistic execution mode; and
in response to being in the pessimistic execution mode, processing reservation requests from on-hold jobs prior to processing reservation requests from new jobs.

### Claim 18

One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause:
receiving, by a resource manager, a reservation request from a job for a graph processing operation, wherein:
the resource manager tracks an amount of available cluster memory for a cluster of machines and an amount of available machine memory in each machine in the cluster, and
the reservation request specifies an identification of the job, a type of reservation, and an amount of memory requested;
determining, by the resource manager, whether to grant the reservation request based on the type of reservation, the amount of memory requested, and the amount of available cluster memory or the amount of available machine memory in one or more machines in the cluster; and
in response to the resource manager determining to grant the reservation request:
sending a response to the job indicating an amount of memory reserved; and
adjusting the amount of available cluster memory and the amount of available machine memory for at least one machine in the cluster based on the amount of memory reserved.

### Claim 19 (depends on 18)

The one or more non-transitory storage media of claim 18, wherein:
the type of reservation is selected from the group consisting of pre-reservation, flexible reservation, or fixed reservation,
the pre-reservation type requests a guarantee that the amount of memory requested is available in the cluster,
the flexible reservation type requests a guarantee that the amount of memory requested is available in the cluster and a guarantee that the amount of memory requested is available in a specified machine within the cluster,
the fixed reservation type requests a guarantee that the amount of memory requested is available in the cluster, a guarantee that the amount of memory requested is available in a specified machine within the cluster, and a guarantee that the amount of memory requested will reside on the specified machine if the job is restarted, and
memory reserved for a reservation request of a pre-reservation type is subsequently bound to one or more machines using one or more subsequent reservation requests of flexible reservation or fixed reservation types.

### Claim 20 (depends on 18)

The one or more non-transitory storage media of claim 18, wherein:
the job commits persistent objects in persistent object memory,
adjusting the amount of available cluster memory and the amount of available machine memory comprises:
determining the amount of available cluster memory as an amount of physical cluster memory minus an amount of memory reserved for all jobs currently executing in the cluster minus an amount of persistent object memory in the cluster; and
determining the amount of available machine memory for a given machine as an amount of physical machine memory for the given machine minus an amount of memory reserved for all jobs currently executing in the given machine minus an amount of persistent object memory in the given machine.
