NVRAM Log File Capacity Tracking via Actual Data Operation Size

Solution Overview

Problem

Existing data storage management systems fail to accurately determine when a nonvolatile random access memory (NVRAM) log file is full due to neglecting the additional memory space required for certain data storage commands, leading to inefficient data transfer processes.

Innovation Solution

A method for transferring data based on the actual size of a data operation, which involves logging operations in NVRAM, determining the additional memory space needed for each operation, and updating the log entry with the actual size, allowing for accurate assessment of NVRAM capacity and timely data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If the NVRAM log file capacity is monitored based on nominal operation size, then the monitoring process is simple, but the determination of when NVRAM is full is inaccurate

Engineering Contradiction:

Improveaccuracy of NVRAM full determinationVSAvoidcomplexity of memory space calculation

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The system performs preliminary calculation of actual memory space requirements for each storage operation before executing it. By determining the actual size (which includes additional memory space for metadata, alignment, and operation overhead) in advance, the system can accurately track NVRAM usage and determine when the log file is truly full, rather than relying on simple nominal size tracking.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the actual memory consumption of each logged operation is calculated and fed back into the NVRAM capacity tracking. This feedback loop ensures that the determination of NVRAM full status is based on real memory usage rather than estimated values, improving measurement precision while maintaining manageable complexity through systematic tracking.

Inventive Principle:

Principle #23Feedback

2Productivity

If data transfer is delayed until NVRAM appears full by nominal size, then system throughput is reduced, but implementation is simpler

Engineering Contradiction:

Improvedata transfer efficiencyVSAvoidwaiting time for client computing devices

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary calculation of actual memory space requirements for each storage operation before executing it. By determining the actual size (which includes additional memory space for metadata, alignment, and operation overhead) in advance, the system can accurately track NVRAM usage and determine when the log file is truly full, rather than relying on simple nominal size tracking.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where the actual memory consumption of each logged operation is calculated and fed back into the NVRAM capacity tracking. This feedback loop ensures that the determination of NVRAM full status is based on real memory usage rather than estimated values, improving measurement precision while maintaining manageable complexity through systematic tracking.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS10057350B2Methods for transferring data based on actual size of a data operation and devices thereof

Publication Date: 2018.08.21 NETAPP INC

AI summary

A method, non-transitory computer readable medium, and device that assists with transferring data based on actual size of a data operation includes receiving a data operation from a client computing device. A type of the received data operation is determined and additional memory size associated with the determined type of the received data operation is identified. Next, a non-volatile log file is updated with the identified additional memory size and the determined type of the received data operation.