Synchronized Reboot Management System for Memory Exhaustion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computing systems with compact operating systems face sluggishness and potential crashes due to excessive memory usage by application software, leading to kernel-released memory reserves, which can cause OS crashes.
Innovation Solution
A management system that continuously monitors memory usage, compares it with predetermined thresholds, and enables a synchronized reboot by backing up data to non-volatile memory and role-swapping between active and standby management systems to prevent memory exhaustion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If application software utilizes excessive memory, then the computing system can perform more operations, but the OS may crash abruptly or become sluggish
Solution Approach 1:
The system performs preliminary actions by monitoring memory usage thresholds and proactively initiating synchronized reboots before memory exhaustion causes OS crashes. The management system continuously tracks memory consumption and triggers preventive measures when thresholds are approached, rather than reacting after crashes occur.
Solution Approach 2:
The system implements feedback mechanisms where the management system monitors memory usage metrics and adjusts system behavior accordingly. When memory thresholds are exceeded, the system initiates synchronized reboots of child systems, creating a closed-loop control system that responds to memory conditions and prevents OS crashes.
2Quantity of substance
If the kernel releases memory reserved for OS level processes, then more memory is available for applications, but the system becomes sluggish
Solution Approach 1:
The system takes preliminary action by initiating synchronized reboots before memory exhaustion occurs, preventing the need for aggressive memory reallocation that would cause sluggishness. The management system proactively manages memory by triggering reboots when thresholds are approached, maintaining system responsiveness.
3Reliability
If the system continuously monitors memory usage and enables synchronized reboot, then OS crashes are minimized, but system complexity increases
Solution Approach 1:
The management system performs multiple functions within a unified framework: it monitors memory usage across child systems, tracks threshold violations, initiates synchronized reboots, and coordinates role swaps between active and standby management systems. This multi-functionality consolidates complexity into a single manageable component.
Solution Approach 2:
The system uses a standby management system as a copy of the active management system. When a synchronized reboot is needed, the standby system takes over the role of the active system, providing a template for failover that simplifies the reboot coordination process.
4Reliability
If role-swapping between active and standby management systems is implemented, then system stability is improved, but the complexity of coordination increases
Solution Approach 1:
The standby management system is prepared in advance as a pre-configured copy of the active system. When a role swap is needed, the standby system can immediately assume the active role without complex real-time configuration, as all necessary settings and states are pre-established during the standby period.
Data Source
AI summary
Examples described herein relate to a system including a first management system having a primary memory including a free memory, a used memory, and a loosely reserved memory, where the loosely reserved memory comprises cache memory having a reclaimable memory; and a processing resource coupled to the primary memory. The processing resource may monitor an amount of the used memory and an amount of an available memory during runtime of the first management system. Further, the processing resource may enable a synchronized reboot of the first management system if the amount of the used memory is greater than a memory exhaustion first threshold or the amount of the available memory is less than a memory exhaustion second threshold, wherein the memory exhaustion first threshold and the memory exhaustion second threshold are determined based on usage of the reclaimable memory and a number of major page faults.