Nonvolatile Memory Read Latency Distribution Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Solid-state nonvolatile memory technologies like flash memory face challenges in maintaining data integrity and operational life due to limited program-erase cycles and increasing read latencies, which are exacerbated by write amplification and data degradation over time.

Innovation Solution

A method is introduced to manage data within nonvolatile media by monitoring and adjusting the probability distribution of read latencies, selectively moving data based on estimated future read latencies to maintain data integrity and reduce write amplification, using a controller with a read latency prediction engine and block manager to optimize storage operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is frequently moved within nonvolatile medium to maintain data integrity, then data integrity is improved, but write amplification increases and operational life decreases

Engineering Contradiction:
Improvedata integrityVSAvoidoperational life
Core Design Contradiction:
ReliabilityVSDuration of action of stationary object

Solution Approach 1:

The system performs preliminary actions by proactively moving data before degradation occurs. The controller monitors storage units and predicts future read latencies, then relocates data in advance to prevent integrity issues, rather than waiting for actual degradation to manifest.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring read latencies and using this information to guide data movement decisions. The controller adjusts data relocation strategies based on observed latency patterns and predicted future performance, creating a closed-loop system that optimizes data integrity while minimizing unnecessary movements.

Inventive Principle:
Principle #23Feedback

2Speed

If data is moved proactively to maintain read latency distributions, then read latency performance is improved, but write amplification increases

Engineering Contradiction:
Improveread latencyVSAvoidwrite amplification
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The system changes parameters by monitoring and responding to read latency metrics. When predicted read latencies exceed thresholds, the system adjusts its data movement strategy, changing the state of storage units from static to relocated, thereby optimizing read performance while minimizing unnecessary write operations.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The controller uses feedback from measured read latencies to dynamically adjust data movement decisions. By continuously monitoring performance metrics and comparing them against targets, the system optimizes the balance between maintaining read latency performance and minimizing write amplification.

Inventive Principle:
Principle #23Feedback

3Loss of time

If data is relocated based on predicted read latencies, then future read latency is improved, but current write operations increase

Engineering Contradiction:
Improvefuture read latencyVSAvoidwrite operations
Core Design Contradiction:
Loss of timeVSProductivity

Solution Approach 1:

The system performs preliminary data relocation based on predicted future read latency patterns. By analyzing historical access patterns and predicting future performance, the system proactively moves data before latency issues occur, optimizing future read operations while managing current write overhead.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies partial action by selectively moving only those data units that are predicted to cause latency issues, rather than performing blanket data migrations. This targeted approach reduces unnecessary write operations while still achieving the goal of maintaining read latency performance.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10387340B1Managing a nonvolatile medium based on read latencies
Publication Date: 2019.08.20 AMAZON TECH INC
  • US10387340B1 patent drawing
  • US10387340B1 patent drawing
  • US10387340B1 patent drawing

AI summary

The following description is directed to managing a nonvolatile medium. The nonvolatile medium can be organized as a plurality of storage units. In one example, a method can include measuring read latencies for the individual storage units of the nonvolatile medium. A probability distribution of future read latencies for the nonvolatile medium can be estimated based on the measured read latencies for the individual storage units of the nonvolatile medium. Information can be moved from a particular storage unit of the nonvolatile medium to a different storage unit of the nonvolatile medium based on the estimated probability distribution of future read latencies for the nonvolatile medium.