Application-Specific Write Budgets for Memory Lifespan

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The phenomenon of SSD wear, caused by increased write requests and write amplification, compromises the expected lifespan of non-volatile memory in computing devices.

Innovation Solution

Establishing application-specific write budgets based on metrics such as write cycle, write amplification, bad block, overprovisioning, storage capacity, configuration type, and age information to manage write requests effectively, thereby preserving the lifespan of non-volatile memory.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If write requests are allowed without restriction to maintain application performance, then application productivity is improved, but non-volatile memory lifespan deteriorates due to excessive write cycles

Engineering Contradiction:
Improveapplication write performanceVSAvoidnon-volatile memory lifespan
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the write budget allocation by dividing it into application-specific write budgets. Instead of treating all write requests uniformly, the system creates individual budgets for each application based on its characteristics and historical behavior. This segmentation allows differential control where critical applications can consume more of the write budget while less critical applications consume less, thereby maintaining overall system productivity while preserving memory lifespan through targeted write rate management.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If write amplification is allowed to occur naturally during SSD operations, then storage flexibility is maintained, but harmful factors increase due to accelerated wear from additional write cycles

Engineering Contradiction:
Improvestorage operation flexibilityVSAvoidwrite amplification wear
Core Design Contradiction:
Adaptability or versatilityVSObject-generated harmful factors

Solution Approach 1:

The patent implements a feedback mechanism that continuously monitors the current health status of the non-volatile memory and the remaining write budget. This feedback loop allows the system to dynamically adjust write operations in real-time. When the memory approaches wear thresholds or when write budget is depleted, the system responds by preventing additional write requests or by migrating data to reduce write amplification. This feedback control maintains storage flexibility while actively mitigating harmful wear effects.

Inventive Principle:
Principle #23Feedback

3Reliability

If data migration is performed frequently to manage write amplification, then non-volatile memory reliability is improved, but loss of time increases due to additional write operations

Engineering Contradiction:
Improvememory block reliabilityVSAvoiddata migration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by proactively managing write budgets before memory wear becomes critical. The system establishes write budgets based on predicted memory lifespan and current health status, preventing excessive write accumulation that would trigger urgent data migration. By planning and controlling write operations in advance within allocated budgets, the system reduces the frequency and urgency of data migration operations, thereby maintaining reliability while minimizing time loss.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3776165B1Techniques for preserving an expected lifespan of a non-volatile memory
Publication Date: 2025.10.01 APPLE INC
  • EP3776165B1 patent drawingFigure 1
  • EP3776165B1 patent drawingFigure 2
  • EP3776165B1 patent drawingFigure 3

AI summary

Disclosed herein is a technique for preserving an expected lifespan of a non-volatile memory that is communicably coupled with a computing device. According to some embodiments, the technique can be implemented by the computing device, and include (1) receiving metrics associated with the non-volatile memory, (2) for each application of a plurality of applications associated with the computing device: establishing, based on the metrics, a respective write budget for the application. According to some embodiments, the respective write budget for each application can be further based on a count of the plurality of applications. Additionally, the technique can further include (3) receiving, from an application of the plurality of applications, a write request directed to the non-volatile memory, and (4) in response to determining that the write request does not violate the respective write budget for the application: issuing the write request to the non-volatile memory.