Ledger-Based Resource Tracking System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing operating systems lack effective real-time resource usage tracking and management, with limited control over resource consumption, leading to impractical recovery from resource allocation failures and inability to track resource usage post-event without prior enablement.
Innovation Solution
A ledger-based system for tracking resource usage that includes a ledger template, objects, and entries, allowing for centralized decision-making, low overhead, and extensibility, with the ability to trigger real-time reactions when resource limits are exceeded by invoking callback functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional accounting features are used to track resource usage, then resource consumption can be recorded, but the tracking can only be done after the fact and requires explicit enabling
Solution Approach 1:
The patent applies preliminary action by pre-configuring ledger templates and registering callback functions before resource consumption occurs. The system proactively sets up tracking infrastructure in advance, so when resources are consumed, the ledger immediately captures the data and triggers appropriate responses without delay. This resolves the contradiction by ensuring both accurate measurement and timely response.
2Adaptability or versatility
If resource limits are set using traditional methods, then resource consumption can be controlled, but the set of controllable resources is limited and cannot be extended
Solution Approach 1:
The patent implements universality through a generic ledger template structure that can track any type of resource. The template includes fields for resource identification, limits, and callback functions that can be configured for different resource types (memory, CPU, I/O, custom resources). This single unified system handles diverse resource types without requiring separate control mechanisms, resolving the contradiction between extensibility and complexity.
Solution Approach 2:
The system applies dynamics by allowing runtime registration of new resource types and dynamic modification of ledger templates. New resources can be added to the tracking system without recompiling or restructuring the entire control framework. The callback mechanism dynamically adapts to different resource types, enabling the system to evolve and accommodate new resource categories as needed.
3Reliability
If traditional signal-based resource limit enforcement is used, then resource overconsumption can be detected, but the process cannot recover and immediately terminates
Solution Approach 1:
The patent implements feedback through callback functions that are triggered when resource limits are approached or exceeded. Instead of immediately terminating the process, the system provides feedback to the process or system administrator, allowing for graceful handling of resource constraints. The callback mechanism enables monitoring, logging, and potential recovery actions, resolving the contradiction between reliable limit enforcement and process recoverability.
Solution Approach 2:
The system applies beforehand cushioning by providing advance warning when resource consumption approaches predefined limits. The callback functions can trigger preventive actions, such as logging warnings, notifying administrators, or initiating cleanup operations before the limit is actually exceeded. This cushioning approach prevents catastrophic failures and allows for smooth transitions or recoveries.
Data Source
AI summary
Disclosed are systems, methods, and non-transitory computer-readable storage media for tracking and managing resource usage through a ledger feature that can trigger complex real-time reactions. The resource tracking can be managed through a ledger module and a ledger data structure. The ledger data structure can be updated each time a task requests a resource. Additionally, as part of the update, the ledger module can verify whether a resource has been over consumed. In response to the detection of an over consumption, the ledger module can set a flag. At some later pointer when the thread is in a stable, well-understood point, the ledger module can check if the flag has been set. If the flag has been set, the ledger module can call the appropriate callback function, which can react to the over consumption in a resource specific manner.