Dynamic Software Rejuvenation Thresholds for Aging Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software rejuvenation methods fail to accurately distinguish between performance degradation caused by bursts of requests and software aging, leading to a gap between user perception and monitoring tool views of performance, and lack effective triggers for proactive system maintenance.
Innovation Solution
A computer-implemented method that uses customer-affecting metrics, such as response times, to dynamically adjust thresholds and trigger software rejuvenation, distinguishing between transient and aging-related degradations by sampling and tracking variability in multiple buckets, and identifying the source of performance issues for targeted rejuvenation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If software rejuvenation is triggered based on fixed thresholds, then the system can detect performance degradation, but it cannot distinguish between bursts of requests and software aging, leading to false triggers or missed detections
Solution Approach 1:
The patent implements dynamic thresholds that automatically adjust based on observed system behavior and request patterns. Instead of using fixed thresholds, the system adapts thresholds in real-time to distinguish between transient load bursts and genuine software aging, resolving the contradiction between detection precision and adaptability
Solution Approach 2:
The system changes threshold parameters dynamically based on system state and observed performance patterns. By adjusting threshold values according to current load conditions and historical data, the system maintains high detection accuracy while adapting to varying operational conditions
2Reliability
If software rejuvenation is triggered frequently to maintain high reliability, then system reliability improves, but unnecessary rejuvenation events increase system complexity and resource consumption
Solution Approach 1:
The system employs feedback mechanisms where performance metrics and request patterns are continuously monitored and fed back into the threshold adjustment logic. This feedback loop enables the system to learn from past behavior and make informed decisions about when rejuvenation is truly necessary, improving reliability while avoiding unnecessary complexity
Solution Approach 2:
The system performs preliminary analysis of request patterns and performance trends before triggering rejuvenation. By evaluating multiple indicators and adjusting thresholds in advance based on observed patterns, the system can distinguish between transient issues and genuine degradation, reducing unnecessary rejuvenation events
3Extent of automation
If monitoring tools use server-based health checks, then system monitoring is implemented, but a gap exists between user perception of performance and monitoring tool view
Solution Approach 1:
The patent introduces customer-affecting metrics as an intermediary between server-based monitoring and user perception. These metrics directly reflect what users experience, bridging the information gap by providing monitoring data that aligns with user-perceived performance rather than just server-side technical metrics
Data Source
AI summary
A computer-implemented method for triggering a software rejuvenation system and/or method includes receiving a request for resources, determining an estimated response time to the request for resources, determining that the estimated response time is greater than a first threshold, determining that a number of estimated response times greater than the first threshold is greater than or equal to a dynamic second threshold, and triggering the software rejuvenation system and/or method.