NVRAM Buffer for Object Storage Write Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current object-based storage systems face challenges in efficiently managing data across multiple storage tiers and types, particularly in handling object versioning, replication, and lifecycle management, which affects performance and reliability as storage needs continue to grow.

Innovation Solution

The implementation of a storage system that utilizes non-volatile random access memory (NVRAM) as a buffer for write operations, offloading device management responsibilities from storage drives, and employing erasure coding and mirroring schemes to ensure data redundancy and availability across multiple storage nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If traditional storage systems use standard storage drives for data management, then device management responsibilities are handled directly by storage drives, but write latency increases and unnecessary write operations occur

Engineering Contradiction:
Improvewrite latencyVSAvoiddevice management responsibilities
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent introduces NVRAM as an intermediary buffer between the storage drive and the data management system. This mediator handles write operations by buffering data temporarily, allowing the storage drive to be offloaded from direct write management responsibilities. The NVRAM buffer resolves the contradiction by providing fast write access (reducing write latency) while the storage drive focuses on persistent storage, separating management responsibilities from execution.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If storage systems implement comprehensive object versioning and replication, then data reliability improves, but system complexity and management overhead increase

Engineering Contradiction:
Improvedata reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complexity of object versioning and replication management from the storage drive itself and relocates it to a centralized storage management system. The storage drive is taken out of the management loop, focusing only on raw storage operations. The management system handles versioning, replication, and data reliability independently, separating the reliability function from the storage hardware complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The storage management system provides self-service capabilities by automatically handling object versioning, replication, and data management without requiring manual intervention. The system monitors and manages its own state, performing necessary operations to maintain data reliability while shielding users from the underlying complexity. This automated self-service approach maintains high reliability while managing complexity internally.

Inventive Principle:
Principle #25Self-service

3Productivity

If storage systems use standard RAM for buffering write operations, then write performance improves, but data loss occurs during power failures

Engineering Contradiction:
Improvewrite performanceVSAvoiddata loss during power failure
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by using NVRAM to buffer write operations before they are permanently committed to the storage drive. This buffer is populated in advance during normal operation, and its contents are automatically flushed to persistent storage when power is restored after a failure. This preliminary buffering action allows for high write performance during operation while ensuring data safety through automatic persistence on power restoration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements beforehand cushioning by using NVRAM as a protective buffer between write operations and persistent storage. This cushion absorbs the impact of power failures by preserving data in the NVRAM buffer during outages and automatically flushing to storage when power returns. The cushioning mechanism protects against data loss while maintaining high write performance during normal operation.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If storage systems implement proactive data rebuilding and redundancy mechanisms, then data availability improves, but write operations become more complex

Engineering Contradiction:
Improvedata availabilityVSAvoidwrite operation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The storage management system provides self-service by automatically monitoring storage node health and performing proactive data rebuilding without intervention. The system detects failures and initiates redundancy operations autonomously, maintaining data availability while shielding write operations from the complexity of these management tasks. Write operations remain simple client-side operations while the system handles redundancy internally.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11995336B2Bucket views
Publication Date: 2024.05.28 PURE STORAGE INC
  • US11995336B2 patent drawing
  • US11995336B2 patent drawing
  • US11995336B2 patent drawing

AI summary

A method of operating an object-based storage system, practiced by the storage system, is provided. The method includes establishing a plurality of buckets for objects, in the storage system and establishing a plurality of bucket views in the storage system, each bucket view supporting access to objects of one of the plurality of buckets. The method includes accessing an object of a bucket through one of the plurality of bucket views.