Dynamic Performance Data Objects in Storage Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for handling performance data in data storage systems lead to resource inefficiencies, as performance objects are cached indefinitely and all clients must process full managed objects to access performance data, even if only some clients need it.

Innovation Solution

Creating a software object to represent managed objects on demand, allowing performance data to be updated frequently and accessed independently, thus freeing up resources when the data is no longer needed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If performance data is cached indefinitely in conventional methods, then data availability is maintained, but system resources are wasted

Engineering Contradiction:
Improvedata availabilityVSAvoidsystem resource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements dynamic creation and destruction of software objects based on real-time demand. Performance software objects are created when performance data is requested and destroyed after a predetermined time period or when no longer needed, transforming the static caching approach into a dynamic resource management system that adapts to actual usage patterns

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent employs short-lived software objects that exist only temporarily to serve performance data requests. Instead of maintaining permanent cached objects, the system creates lightweight objects on-demand that are automatically destroyed after use, reducing resource consumption while maintaining data availability

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

2Ease of operation

If all clients process full managed objects to access performance data, then data access is simplified, but processing efficiency decreases

Engineering Contradiction:
Improvedata access simplicityVSAvoidprocessing efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent extracts performance data from the full managed object structure by creating separate, dedicated software objects that contain only performance-related information. This allows clients to access performance data without processing unnecessary managed object properties, improving processing efficiency while maintaining ease of access

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent segments performance data into independent software objects that are separate from the main managed objects. This segmentation allows clients to request and process only the performance data they need, rather than handling complete managed objects, thereby improving processing efficiency

Inventive Principle:
Principle #1Segmentation

3Speed

If performance objects are cached for the lifetime of the management session, then data access speed is improved, but memory consumption increases

Engineering Contradiction:
Improvedata access speedVSAvoidmemory consumption
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent implements periodic creation and destruction of performance software objects rather than continuous caching. Objects are created when needed, remain active for a predetermined time period or until requested again, and are then destroyed, creating a rhythmic pattern of resource allocation that balances access speed with memory consumption

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent transforms the static memory allocation model into a dynamic one where software objects are allocated and deallocated based on actual access patterns. This dynamic approach allows the system to maintain fast access speeds for active objects while freeing memory for objects that are no longer needed

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9146734B1Handling managed object data
Publication Date: 2015.09.29 EMC IP HLDG CO LLC
  • US9146734B1 patent drawing
  • US9146734B1 patent drawing
  • US9146734B1 patent drawing

AI summary

A method is used in handling managed object data. A software object is created which represents a managed object in a data storage system. The software object holds performance data for the managed object. The software object is created in response to a request for the performance data. Based on a determination that the performance data held by the software object is out of date, the software object is destroyed.