Distributed Fabric Switches for HPC Cluster I/O Bottlenecks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

High Performance Computing (HPC) systems face limitations in scalability and reliability due to imbalanced processing, memory, and I/O bandwidth, leading to inadequate I/O performance and increased costs, with conventional HPC environments often lacking robust cluster management software for efficient operation.

Innovation Solution

A cluster management system and method that includes cluster agents and a management engine, dynamically allocating HPC nodes based on status to achieve balanced architecture, reducing centralized switching functionality, and optimizing I/O performance, scalability, and fault tolerance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If conventional HPC environments use centralized switching functionality, then system architecture is simplified, but I/O performance is limited and does not scale well

Engineering Contradiction:
Improvesystem architectureVSAvoidI/O performance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments the centralized switching functionality into distributed fabric switches located at each blade. Each blade incorporates its own fabric switch, eliminating the bottleneck of centralized switching and enabling parallel I/O operations across multiple blades, thereby significantly improving I/O performance while maintaining architectural simplicity through modular design

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transitions from a single-dimensional centralized switching architecture to a multi-dimensional distributed fabric architecture. By introducing fabric switches at each blade level and creating a mesh-like interconnect topology, the system adds spatial dimensions to data flow paths, enabling simultaneous multi-path I/O operations and dramatically increasing bandwidth capacity

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If HPC clusters are built with blades having many components, then functionality is enhanced, but reliability is dramatically reduced

Engineering Contradiction:
ImprovefunctionalityVSAvoidsystem reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent extracts only the essential components needed for HPC functionality from each blade, removing unnecessary components that would reduce reliability. Each blade is configured with precisely the components required for computing and fabric communication, eliminating the reliability penalty of over-provisioning while maintaining full functional capability through the distributed fabric architecture

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies local quality by customizing each blade's component configuration to match its specific functional role. Rather than uniformly equipping all blades with maximum components, each blade receives exactly the components it needs for its designated function, optimizing both reliability and functionality through localized component selection

Inventive Principle:
Principle #3Local quality

3Ease of manufacture

If processing, memory, and I/O bandwidth are not well balanced, then hardware costs are reduced, but scalability is limited

Engineering Contradiction:
Improvehardware costsVSAvoidscalability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements dynamic resource allocation and balancing across processing, memory, and I/O bandwidth through the distributed fabric architecture. The system can dynamically adjust resource distribution based on workload demands, allowing optimal scaling of HPC applications while maintaining cost-effectiveness through on-demand resource utilization rather than static over-provisioning

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables parameter changes in the HPC system by allowing dynamic adjustment of processing power, memory allocation, and I/O bandwidth utilization. The distributed fabric architecture permits independent scaling of these parameters based on application requirements, achieving well-balanced performance without excessive hardware costs through flexible parameter optimization

Inventive Principle:
Principle #35Parameter changes

4Device complexity

If centralized management is used, then system control is simplified, but cluster management robustness is insufficient for production environments

Engineering Contradiction:
Improvemanagement controlVSAvoidcluster management robustness
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments cluster management functions into distributed agents running on each blade rather than relying solely on centralized management. Each agent independently monitors and manages its local blade resources, providing robustness against centralized failures while maintaining simplified control interfaces through coordinated agent-collector architecture

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements feedback mechanisms where distributed management agents continuously report blade status, performance metrics, and resource utilization to a management collector. This feedback loop enables automatic adaptive management decisions, enhancing robustness for production environments while maintaining simplified control through rule-based automated responses

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9178784B2System and method for cluster management based on HPC architecture
Publication Date: 2015.11.03 RAYTHEON CO
  • US9178784B2 patent drawing
  • US9178784B2 patent drawing
  • US9178784B2 patent drawing

AI summary

Cluster management software comprises a plurality of cluster agents, with each cluster agent associated with an HPC node including an integrated fabric and the cluster agent operable to determine a status of the associated HPC node. The software further includes a cluster management engine communicably coupled with the plurality of the HPC nodes and operable to execute an HPC job using a dynamically allocated subset of the plurality of HPC nodes based on the determined status of the plurality of HPC nodes.