<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>NAND Flash on Nalar</title>
    <link>https://nalar.dev/tags/nand-flash/</link>
    <description>Recent content in NAND Flash on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/nand-flash/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SSD Write Cache and Sustained Transfer Speed</title>
      <link>https://nalar.dev/ssd-write-cache-and-sustained-transfer-speed/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/ssd-write-cache-and-sustained-transfer-speed/</guid>
      <description>&lt;p&gt;An SSD can copy the first part of a large file at high speed, then settle at a much lower rate even though nothing else appears to have changed. That drop can be normal. Many consumer SSDs use part of their NAND as a fast write cache, allowing short bursts to finish before the drive has to sustain writes in its denser storage mode.&lt;/p&gt;&#xA;&lt;p&gt;This behavior makes a single peak transfer number a poor description of every write workload. Cache size, free space, NAND type, controller policy, temperature, and the amount of data already waiting inside the drive can all affect the speed seen during a long transfer.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Flash Wear Leveling Spreads Writes Across NAND Cells</title>
      <link>https://nalar.dev/flash-wear-leveling-spreads-writes-across-nand-cells/</link>
      <pubDate>Mon, 14 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/flash-wear-leveling-spreads-writes-across-nand-cells/</guid>
      <description>&lt;p&gt;A file can keep the same name and logical location while its bytes move through many different physical locations inside an SSD, phone, memory card, or USB drive. That movement is not a side effect of a messy file system. It is a core part of managing NAND flash.&lt;/p&gt;&#xA;&lt;p&gt;Flash memory has a finite program-and-erase endurance. Rewriting the same physical area continuously would age that area much faster than the rest of the device. Controllers avoid that pattern by spreading writes across available flash. This process is called wear leveling.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
