hesela.devHot/cold data separation
A flash-placement strategy that groups data by update frequency so frequently overwritten pages and long-lived pages need not share the same cleaning pool.
Hot and cold refer to update frequency, not physical temperature or hot/cold storage tiers. Spare-space allocation between pools matters alongside classification and block selection.
Relations
- related
- greedy-garbage-collection, garbage-collection, over-provisioning, ftl
Limitations
- Data classification can change with workload; a placement model is not evidence that every controller implements it. [1]