Diagnostic Data Component Memory Dump Resource Boost

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Capturing system memory dumps in computing systems is a time-consuming and resource-intensive process that can cause significant delays and impact system performance, particularly when dealing with non-fatal errors and undetected issues that require manual initiation and involve multiple memory spaces.

Innovation Solution

A computer-implemented method that includes a diagnostic data component requesting a computing resource boost when a system memory dump meets predetermined criteria, allowing additional processing power to expedite the data capture and reduce overall dump capture times, thereby minimizing the impact on system performance and backlog.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a system memory dump is captured using standard resources, then complete diagnostic data is collected, but system performance is significantly degraded and capture time is extended

Engineering Contradiction:

Improvediagnostic data completenessVSAvoidsystem performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adjusts processing resources allocated to the memory dump capture operation. When a memory dump is initiated, the system temporarily boosts processing power and resources specifically for the diagnostic data collection process, then restores normal resource allocation afterward. This dynamic resource management ensures complete data collection while minimizing impact on ongoing system operations.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The system changes operational parameters during the memory dump process by activating enhanced processing modes and adjusting resource allocation parameters. This includes modifying processor scheduling parameters, memory access patterns, and I/O operation parameters to optimize the balance between data collection completeness and system performance maintenance.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If a system memory dump is captured using standard resources, then diagnostic data is collected, but capture duration is significantly extended

Engineering Contradiction:

Improvediagnostic data collectionVSAvoiddump capture time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-allocating and pre-configuring enhanced processing resources before the memory dump capture begins. This includes pre-warming processing pipelines, pre-allocating buffer memory, and pre-configuring I/O channels to ensure that when the dump operation starts, maximum processing capacity is immediately available, reducing overall capture time.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements rushed processing for critical memory dump operations by prioritizing the diagnostic data collection process over other non-critical system operations. This involves skipping normal scheduling delays, using direct memory access paths, and employing optimized data transfer mechanisms to rapidly complete the capture process while maintaining data integrity.

Inventive Principle:

Principle #21Skipping (Rushing through)

3Loss of time

If additional computing resources are allocated for memory dump capture, then capture time is reduced, but system resource availability for other processes is decreased

Engineering Contradiction:

Improvedump capture timeVSAvoidcomputing resource availability

Core Design Contradiction:

Loss of timeVSQuantity of substance

Solution Approach 1:

The system implements periodic resource allocation where enhanced processing resources are temporarily activated only during the brief window when memory dump capture is required, then deactivated to restore full resource availability. This periodic boosting of resources achieves fast capture times while ensuring that computing resources remain available for other processes during normal operation periods.

Inventive Principle:

Principle #19Periodic action

Solution Approach 2:

The system applies partial resource allocation by providing enhanced processing power only for the specific duration and scope of the memory dump operation, rather than permanently allocating excessive resources. This allows the system to achieve reduced capture times through temporary resource intensification while maintaining adequate resource availability for other processes during normal operation.

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS11656930B2Minimizing impact of first failure data capture on computing system using recovery process boost

Publication Date: 2023.05.23 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A computer-implemented method for capturing system memory dumps includes receiving, by a diagnostic data component, an instruction to capture a system memory dump associated with a computer process being executed by a computing system comprising one or more processing units, the system memory dump comprising data from a plurality of memory locations associated with the computer process. In response to determining that the system memory dump satisfies a predetermined criterion, the diagnostic data component sends a request for a computing resource boost from the computing system. Further, in response to the request for the computing resource boost being granted, the diagnostic data component uses additional computing resources from the one or more processing units to store the data from the plurality of memory locations in the system memory dump and executing the backlogged operations that were halted due to the system memory dump capture.