Remote Server Performance Correction via Inversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for addressing performance issues in distributed transactions often fail to completely resolve problems by focusing on the affected machine alone, neglecting the potential for corrective actions on other nodes that may be the true source of the issue.

Innovation Solution

A system that monitors business transactions and applies corrective actions to nodes other than the one experiencing a performance issue, using a controller with health rules and policies to determine the appropriate action based on performance metrics, allowing for the identification and resolution of issues across the distributed system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If corrective actions are applied only to the node experiencing the performance issue, then the response time is reduced, but the reliability is worsened because the root cause may lie in another node

Engineering Contradiction:
Improveresponse timeVSAvoidproblem resolution effectiveness
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

Instead of applying corrective actions to the node where the performance issue is detected, the system inverts the approach by identifying and applying actions to other nodes in the distributed system that may be the true source of the problem. The controller analyzes transaction flows and determines that a performance metric violation at node A may be caused by an issue at node B, thereby applying the corrective action to node B rather than node A.

Inventive Principle:
Principle #13The other way round (Inversion)

2Measurement precision

If the system monitors and analyzes transaction flows across all nodes, then the measurement precision of performance issues is improved, but the device complexity increases

Engineering Contradiction:
Improveperformance issue identification accuracyVSAvoidmonitoring system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The controller acts as an intermediary that receives performance data from multiple nodes, analyzes transaction flows, and determines the root cause of performance issues. Rather than requiring direct monitoring and analysis at each node, the controller centralizes the analytical function, simplifying the overall system architecture while maintaining high measurement precision through comprehensive transaction flow analysis.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS10452469B2Server performance correction using remote server actions
Publication Date: 2019.10.22 CISCO TECHNOLOGY INC
  • US10452469B2 patent drawing
  • US10452469B2 patent drawing
  • US10452469B2 patent drawing

AI summary

Business transactions and the nodes processing the transactions may be monitored. Actions may be applied to one or more nodes when a performance issue is detected. A performance issue may relate to a metric associated with a transaction or node that processes the transaction. If a performance metric does not satisfy a health rule, the policy determines which action should be performed to correct the performance of the node. The corrective action may be applied to a node other than the node at which the performance metric is associated with. For example, if a performance metric for a first node does not satisfy a threshold, the corrective action may be applied to a second node. When a solution applied to a second node is found to correct the problem in first node, the solution may be applied to the other nodes experiencing the same problem.