SSD Simulator
All graphs
Validation

Granularity Bracket — FEMU between block & superblock GC

Our finding. The gap between the simulator and FEMU is explained by exactly one mechanism: garbage-collection erase granularity. Running the same workload with block- and superblock-granular GC brackets FEMU's value — on prxy_0, 1.54 (block) ≤ 1.873 (FEMU) ≤ 2.14 (superblock). The ~40% swing from the granularity switch contains FEMU's number.

How this helps our work. It turns an apparent discrepancy into a controlled, understood modeling parameter. We can read every sim–FEMU comparison correctly, and tune the simulator to a target device's erase granularity for an exact match — important because real NAND erases at superblock granularity for parallelism.

What it shows. The same conventional workload three ways: EyanaSSDSim block GC, FEMU (superblock erase), EyanaSSDSim superblock GC. Coarser erase reclaims a whole line together, migrating more valid pages → higher WAF; block reclaim can take the single emptiest block → fewer migrations → lower WAF.

What we found
Granularity Bracket — FEMU between block & superblock GC
Previous← Validation — EyanaSSDSim vs FEMU (WAF)
NextWrite Amplification by Engine across Real Traces →
← Back to all graphs