Solidkor Inc. Technology: Write Endurance

- Home
- Documentation
- Design Support
- Contact Us

NAND write endurance limit - 100,000 Erase/Write cycles per block
Flash memory possesses a finite erase/program cycle capability.

The MLC NAND datasheets guarantee at least 10,000 such cycles per physical block.

The SLC NAND datasheets guarantee at least 100,000 cycles.

Field deployments indicate that each SLC NAND block can be typically erased and programmed 200,000 to 1,000,000 times (or even more) before the end of life.

NAND wear out is manifested by Flash controller inability to erase, or program, the cell within the allocated time.

- Is NAND write endurance a problem for Flash SSD users?

For many years Flash storage manufacturers tried to convince their customers that write endurance is a problem of the past. Effectively, wear-leveling combined with EDC /ECC techniques made Flash based storage devices bullet proof for consumer, and most industrial and defense storage products.

These devices have operated at relatively low transfer rates. The majority of applications were read intensive. In addition, the industrial and defense customers typically controlled system design and worked with Flash SSD manufacturers to ensure that write endurance is not a limiting factor.

These applications did not push Flash write endurance to its limits. It is quite comforting to realize that SLC NANAD based Flash SSD when overwritten once per day, would reach write endurance limit in about 250 years.

Today, Flash SSD's achieved sufficient capacity and performance to be deployed in main stream notebook, server, data recorders and similar performance intensive applications. The Flash memory transformation from niche to core storage technology is in the making.

These new applications will define the new limits for Flash SSD's.

Today's Flash SSDs support sustained writing speed of up to 100 plus MB/s. A 64GB drive would be overwritten 135 times per day. The drive will reach its write endurance within 2 years of such operations.

The MS Windows uses various log files. 4kB of data is written to the log file every second. The majority of high end Flash SSD's use dynamic wear leveling. With no additional steps, the write endurance limits could be reached within months of operations in such system.

The Flash SSD industry, including Solidkor, believes that Flash memory will seriously challenge the HDD supremacy as primary computer storage. Solidkor also believes that the industry has not reached the deployment levels that allow substantiating the theoretical so far "no problem" claim.

Flash SSD features such as SMART support enabling monitoring of the NAND usage is an indispensible tool.

The Flash SSD industry has to continue openly discussing and monitoring the Flash SSD write endurance performance before it disappears from the specifications.

It is also our obligation to ensure that factors influencing write endurance are known.

- Solidkor uses S.M.A.R.T. and LED to monitor NAND usage

Managing write endurance limit in Flash SSD
Let's first review basic Flash memory organization and NAND operations. It helps to understand the relationship between application and Flash SSD life expectancy prediction.

- Flash SSD memory is organized in sectors, pages and blocks

- Three basic NAND operations

- Wear leveling and block sparing techniques manage write endurance

- Dynamic Wear Leveling is perfect enough. Static Wear Leveling is perfect

Wear leveling uses blocks within the boundaries of one wear leveling zone. Some of those blocks may contain so called "static" data. The "static" indicates rarely modified data. Examples may include OS or user files.

The dynamic wear leveling excludes the blocks with the "static" data from the wear leveling. Consider a hypothetical 4000 wear leveling zone where 3500 blocks contain "static" data and the remaining 500 blocks are part of the wear leveling pool. The dynamic wear leveling would spread the writes among the 500 blocks only. The drive could fail prematurely because wear leveling was unable to spread the use among the blocks containing the "static" data.

When "static" data is modified however, wear leveling moves the entire block content to a new location and the block will be placed in the wear leveling block pool.

The dynamic wear leveling could be compared to a tire maintenance process that uses tire rotation and spare tires. The tires installed on a car are an equivalent of blocks in the wear leveling pool. The spare tires are an equivalent of blocks with the "static" data. Dynamic wear leveling action is like effecting a tire rotation. This evens out the wear of tires installed on the car.

Writing to a block with the "static" data is like replacing the tire installed with the spare tire. This helps to even out the wear among spare and installed tires.

Bottom line for the dynamic wear leveling is that if drive content changes from time, all blocks will experience similar usage during Flash SSD life time.

Some applications however, such as those that use file system, may push to the limit the dynamic wear leveling capability. For example, the drive area storing FAT and metadata may experience many more erases/writes than other areas of the wear leveling zone and/or disk.

The static wear leveling would help to address this challenge. It ensures that all blocks within the wear leveling zone, regardless if they contain "static" data or not, are subject to same level of usage. The static wear leveling would move the "static" data from one location to other, transparently to the host depending exclusively on block usage criteria.

While static wear leveling benefits MLC NAND based storage, virtually all industrial grade flash products use today dynamic wear leveling. When combined with the SLC NAND, it provides a very good flash SSD life expectancy for most high end applications.

- Sequantial write makes wear leveling irrelevant

- Wear leveling is everything when writing conitunously to one sector

- Predicting Flash SSD life expectancy