Selective Pruning of I/O Configuration Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for comparing and reconfiguring input/output (I/O) configurations in computing environments are computationally expensive and resource-intensive, especially in resource-constrained environments, due to the complexity and size of I/O configurations, leading to inefficient resource utilization and increased network traffic.
Innovation Solution
The method involves normalizing hierarchical models of existing and desired I/O configurations using syntactical transformation rules, creating hash tree representations, and selectively pruning nodes based on checksum values to reduce the size of I/O reconfiguration requests and free up resources, allowing for faster comparisons and reduced network traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a complete I/O configuration comparison is performed to identify changes, then configuration accuracy is improved, but computational resource consumption increases
Solution Approach 1:
The patent segments the I/O configuration into a hierarchical structure with device-level, component-level, and parameter-level nodes. This segmentation allows the comparison process to focus only on relevant portions of the configuration rather than processing the entire configuration tree, thereby reducing computational resource consumption while maintaining comparison accuracy.
Solution Approach 2:
The patent extracts and compares only the changed portions of the I/O configuration by identifying differences at the device, component, or parameter level. This extraction approach eliminates the need to process unchanged configuration data, significantly reducing computational resource consumption while preserving configuration comparison accuracy.
2Adaptability or versatility
If the I/O configuration size increases to accommodate more devices, then system functionality is improved, but comparison processing time increases
Solution Approach 1:
The hierarchical segmentation of I/O configuration enables the system to handle larger configurations by organizing devices, components, and parameters into a tree structure. This segmentation allows the comparison process to traverse only the necessary paths in the configuration tree, maintaining fast processing times even as system functionality and configuration size increase.
Solution Approach 2:
The patent performs preliminary normalization of the I/O configuration data before comparison, converting configuration data into a standardized hierarchical format. This preliminary action prepares the data for efficient processing and enables faster comparison operations as the configuration size grows.
3Measurement precision
If detailed I/O configuration data is transmitted for reconfiguration, then reconfiguration accuracy is improved, but network traffic increases
Solution Approach 1:
The patent extracts only the changed portions of the I/O configuration (device-level changes, component-level changes, or parameter-level changes) and transmits only these differences for reconfiguration. This extraction approach maintains reconfiguration accuracy by preserving all necessary change information while significantly reducing the quantity of data transmitted over the network.
Solution Approach 2:
Instead of transmitting the complete I/O configuration for reconfiguration, the patent inverts the approach by transmitting only the differences from the baseline configuration. This inversion strategy reduces network traffic while maintaining reconfiguration accuracy, as the receiving system can apply the transmitted differences to the existing baseline configuration.
Data Source
AI summary
An embodiment of the invention may include a method, computer program product, and computer system for reconfiguration of a computing environment from an as-is input/output (I/O) configuration to a to-be I/O configuration. An embodiment may include normalizing respective hierarchical models of the as-is and the to-be I/O configurations. The hierarchical models each comprise a hierarchical structure of leaf and non-leaf nodes. Normalizing comprises the application of syntactical transformation rules to the hierarchical models such that their respective I/O configurations are defined in a syntactically consistent manner. An embodiment may include creating respective hash tree representations of the first hierarchical model and the second hierarchical model. Nodes of the hash tree representations are checksum values. Nodes of the hash tree representations reflect the hierarchical structure of their respective hierarchical models. An embodiment may include pruning one or more nodes of the hash tree representations.