Fragmentation-Based Memory Block Selection for Storage Latency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory systems face increased latency and power consumption when storing large files due to severe fragmentation of memory blocks, which leads to data being spread across many blocks, exacerbating storage and retrieval times.
Innovation Solution
Implementing a fragmentation-based write procedure that selects mildly fragmented blocks for file storage, reducing the number of blocks used and thereby decreasing storage and retrieval times, as well as power consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data is stored in severely fragmented memory blocks, then memory capacity is utilized, but latency and power consumption increase due to data being spread across many blocks
Solution Approach 1:
The system changes the selection criterion for memory blocks from address-based to fragmentation-based. By evaluating fragmentation parameters (such as the number of blocks containing valid data) and selecting blocks below a threshold, the system optimizes write operations to use fewer blocks, thereby reducing latency and improving storage speed
Solution Approach 2:
The system performs preliminary evaluation of memory block fragmentation status before writing data. By pre-assessing which blocks have low fragmentation (fewer valid data blocks), the system prepares optimal storage locations in advance, avoiding the need to scatter data across many fragmented blocks during the write operation
2Productivity
If data is stored in severely fragmented memory blocks, then memory capacity is utilized, but power consumption increases due to increased storage and retrieval operations
Solution Approach 1:
The system changes the selection criterion for memory blocks from address-based to fragmentation-based. By evaluating fragmentation parameters (such as the number of blocks containing valid data) and selecting blocks below a threshold, the system optimizes write operations to use fewer blocks, thereby reducing latency and improving storage speed
Solution Approach 2:
The system performs preliminary evaluation of memory block fragmentation status before writing data. By pre-assessing which blocks have low fragmentation (fewer valid data blocks), the system prepares optimal storage locations in advance, avoiding the need to scatter data across many fragmented blocks during the write operation
3Device complexity
If traditional write procedures are used, then simplicity is maintained, but garbage collection operations increase due to severe fragmentation
Solution Approach 1:
The system implements a feedback mechanism that continuously monitors the fragmentation status of memory blocks. By tracking the number of valid data blocks in each memory block and using this information to guide future write operations, the system dynamically adapts its block selection strategy to minimize fragmentation and reduce garbage collection requirements
Solution Approach 2:
The system changes the selection criterion for memory blocks from address-based to fragmentation-based. By evaluating fragmentation parameters (such as the number of blocks containing valid data) and selecting blocks below a threshold, the system optimizes write operations to use fewer blocks, thereby reducing latency and improving storage speed
Data Source
AI summary
Methods, systems, and devices for access of a memory system based on fragmentation are described. The memory system may receive a first message indicating a set of data that the memory system is to store using a fragmentation-based write procedure. The memory system may, based on the first message, determine blocks of a memory device that satisfy a fragmentation threshold. After determining the blocks, the memory system may transmit to the host system a second message that indicates the memory system is ready to receive the set of data indicated in the first message. The memory system may then store the set of data in the determined blocks based on transmitting the second message.


