Dynamic Checkpointing for Data Processing Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current checkpointing methods in data processing systems allocate resources inefficiently, as they checkpoint processes with equal frequency, leading to significant resource wastage and slower machine performance due to the need to frequently save and restore process states, especially when dealing with multiple processes of varying criticality.

Innovation Solution

A method and system that determine the criticality of each process relative to others and generate a checkpointing schedule accordingly, allowing more critical processes to be checkpointed more frequently, thereby optimizing resource allocation and improving system efficiency by reducing unnecessary checkpointing of less critical jobs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all processes are checkpointed with equal frequency, then data loss risk is minimized for all processes, but resource efficiency deteriorates due to unnecessary frequent checkpointing of non-critical processes

Engineering Contradiction:
Improvedata loss riskVSAvoidresource efficiency
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by assigning different checkpointing frequencies to different processes based on their criticality levels. Critical processes receive higher checkpointing frequencies while non-critical processes receive lower frequencies, optimizing resource allocation according to actual needs rather than applying a uniform approach to all processes.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system dynamically changes the checkpointing frequency parameter based on process criticality assessment. By adjusting this key parameter according to process importance, the system achieves both reliable data protection for critical processes and improved resource efficiency for non-critical processes.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If critical processes are checkpointed more frequently, then data loss risk for critical processes is reduced, but resource consumption increases

Engineering Contradiction:
Improvedata loss risk for critical processesVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements local quality by tailoring checkpointing resources specifically to critical processes that require enhanced protection. Non-critical processes receive reduced checkpointing frequency, thereby freeing resources to be allocated to critical processes without proportionally increasing overall system resource consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system applies partial action by providing enhanced checkpointing frequency only to the extent necessary for critical processes. Rather than uniformly increasing checkpointing for all processes, the system applies excessive checkpointing only where needed (critical processes) and standard or reduced checkpointing elsewhere, optimizing the balance between reliability and resource consumption.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If checkpointing frequency is increased for all processes, then system reliability improves, but machine performance deteriorates due to frequent save and restore operations

Engineering Contradiction:
Improvesystem reliabilityVSAvoidmachine performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent resolves this contradiction by applying different checkpointing frequencies locally to different processes based on their criticality. Critical processes receive higher frequencies to maintain reliability, while non-critical processes receive lower frequencies to preserve overall machine performance, achieving a differentiated optimization strategy.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system applies excessive checkpointing frequency only partially to critical processes rather than to all processes. This selective approach ensures that reliability is enhanced where it matters most while minimizing the performance penalty across the entire system.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11586510B2Dynamic checkpointing in a data processing system
Publication Date: 2023.02.21 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11586510B2 patent drawing
  • US11586510B2 patent drawing
  • US11586510B2 patent drawing

AI summary

Dynamic checkpointing can include determining, using a processor, a process criticality corresponding to a process configured to execute on computer hardware. The process criticality indicates a priority of the process relative to at least one other process configured to execute on the computer hardware. A checkpoint schedule can be generated, using the processor and based on the process criticality, for checkpointing the process when it executes on the computer hardware.