Node-to-Node Process Migration via Page Recency Metadata Cloning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy approaches to node-to-node process migration in computing systems fail to transfer page recency metadata effectively, leading to sub-optimal performance due to the need for the target node to rebuild metadata and resulting in inefficient page management and increased CPU cycles.

Innovation Solution

The implementation of virtual page cache recency metadata state cloning techniques that transfer page recency metadata from a source node to a target node, optimizing data organization and communication paths to reduce memory usage, processing power, and network bandwidth, thereby improving the performance of migrated processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If page recency metadata is not transferred during node-to-node process migration, then the migration process is simpler, but the target node must rebuild metadata consuming excessive CPU cycles and time

Engineering Contradiction:
Improvemigration speedVSAvoidmetadata rebuild time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by capturing and transferring page recency metadata from the source node before the migration is complete. This metadata is prepared in advance and transmitted to the target node during the migration process, so that when migration finishes, the target node already has the recency information ready without needing to rebuild it, thus resolving the contradiction between simple migration and fast metadata availability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a duplicate of the page recency metadata from the source node and transferring it to the target node. Instead of rebuilding metadata at the target, the system copies the existing metadata structure and recency information, significantly reducing the time and CPU cycles required while maintaining migration simplicity

Inventive Principle:
Principle #26Copying

2Productivity

If page recency metadata is transferred from source to target node, then performance of migrated process is improved, but network bandwidth usage increases

Engineering Contradiction:
Improvemigrated process performanceVSAvoidnetwork bandwidth
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent applies extraction by separating the page recency metadata from the actual page data during migration. Only the metadata (which is much smaller in size compared to full page contents) is extracted and transferred over the network. This selective extraction improves migrated process performance while minimizing network bandwidth consumption, as the metadata represents only the essential recency information needed for optimal page management at the target node

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses parameter changes by transferring only the recency metadata parameters (which describe page access patterns) rather than the actual page content parameters. This change in what is being transferred - from full page data to metadata descriptors - significantly reduces network bandwidth requirements while still enabling performance improvement at the target node through accurate page recency tracking

Inventive Principle:
Principle #35Parameter changes

3Loss of energy

If the target node rebuilds page recency metadata from scratch, then network bandwidth is saved, but CPU cycles and memory usage increase significantly

Engineering Contradiction:
Improvenetwork bandwidthVSAvoidCPU cycles
Core Design Contradiction:
Loss of energyVSUse of energy by moving object

Solution Approach 1:

The patent applies preliminary action by having the source node prepare and transfer the page recency metadata before the target node needs to use it. This preliminary preparation and transfer of metadata avoids the need for the target node to perform computationally intensive metadata reconstruction, thereby reducing CPU cycle usage at the target while having already consumed minimal network bandwidth during the efficient metadata transfer phase

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by duplicating the page recency metadata from the source node and transmitting it to the target node. This copying approach eliminates the need for the target node to rebuild metadata from scratch, significantly reducing target node CPU cycles and memory usage. The network bandwidth consumed during this copy operation is far less than the computational resources saved at the target node

Inventive Principle:
Principle #26Copying

4Productivity

If accurate page recency information is provided at the target node, then page management efficiency is improved, but the complexity of the migration process increases

Engineering Contradiction:
Improvepage management efficiencyVSAvoidmigration process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent uses copying to transfer page recency metadata from source to target node, which provides accurate page recency information for improved page management efficiency. The copying mechanism is implemented by extending the existing migration framework to include metadata transfer, adding minimal complexity while delivering significant performance benefits through accurate recency tracking that enables optimal page caching and eviction decisions at the target node

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20240143389A1High performance node-to-node process migration
Publication Date: 2024.05.02 NUTANIX INC
  • US20240143389A1 patent drawing
  • US20240143389A1 patent drawing
  • US20240143389A1 patent drawing

AI summary

Methods, systems, and computer program products for high-performance multi-node computing. Upon receiving a request to move a computing process from a first computing node to a second computing node, an agent responds to the request by: copying contents of one or more pages of the computing process from the first computing node to the second computing node, identifying page recency metadata corresponding to the one or more pages of the computing process, and copying all or portions of the identified page recency metadata to the second computing node. When the CPU of the second computing node accesses pages of the moved computing process, the operating system of the second computing node observes page recency metadata that had been copied from the first node and stored at the second computing node. The computing process might comprise a virtual machine, a guest operating system, or an executable container.