Database Event Management for Consistent Response Times
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workload management techniques in computing systems fail to effectively manage unforeseen impacts such as request volume surges, shared resource exhaustion, and external conditions like component outages, leading to inconsistent response times and inadequate system regulation.
Innovation Solution
A method and system for monitoring events impacting database system performance and availability, identifying event types, and initiating appropriate actions, including categorizing events as resolvable or unresolvable, and selecting or logging actions accordingly, with the ability to inform users or administrators and dynamically adjust resource allocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If rule-based workload management is used in a controlled environment, then system performance is maintained, but the system fails to respond effectively to external impacts such as request volume surges and component outages
Solution Approach 1:
The patent implements a feedback mechanism where the system continuously monitors system conditions and event states, then automatically adjusts workload management rules based on the current situation. This closed-loop feedback enables the system to adapt to external impacts like request volume surges and component outages while maintaining performance consistency through automated rule adjustments.
Solution Approach 2:
The system transitions from static rule-based workload management to dynamic rule adjustment. Workload management rules are no longer fixed but are automatically modified in response to changing system conditions and events, allowing the system to adapt its behavior dynamically to external impacts while maintaining performance goals.
2Measurement precision
If manual event detection is performed by system administrators, then some events are identified, but corrective action is delayed or incorrect due to human response time and expertise limitations
Solution Approach 1:
The system implements self-service automation where the workload management system automatically detects events, classifies them, and executes corrective actions without human intervention. This eliminates the delays and errors associated with manual administrator response while maintaining precise event detection through automated monitoring and classification mechanisms.
Solution Approach 2:
An automated event classification and rule selection mechanism acts as an intermediary between event detection and corrective action execution. This intermediary layer automatically processes events, determines appropriate responses based on predefined rules, and executes actions, replacing the human administrator's role and eliminating response delays.
3Reliability
If the system monitors and responds to all system conditions and events, then consistent response times are achieved, but system complexity increases
Solution Approach 1:
The system segments event monitoring and rule management into distinct, modular components. Events are classified into specific types (system availability, system performance, operating environment), and separate rules are defined for each event type. This segmentation makes the complex system manageable and maintainable while enabling comprehensive monitoring and consistent response times.
Solution Approach 2:
The system manages complexity by parameterizing workload management rules with configurable thresholds, targets, and actions. Instead of hardcoding complex logic, the system uses parameter-based rule definitions that can be adjusted without changing the underlying system structure, enabling consistent response times while maintaining manageable system complexity.
Data Source
AI summary
The claimed invention provides a method for managing response time in a database system. The method includes monitoring a plurality of events that impact on the operation of the database system, identifying at least one event that impacts on at least one of the performance and availability of the database, and initiating an action in response to the identified event.