Log-structured file system: Difference between revisions

Content deleted Content added
Melancholie (talk | contribs)
Line 35:
* The [[design rationale]] for log-structured file systems assumes that most reads will be optimized away by ever-enlarging memory caches. This assumption does not always hold:
** On magnetic media—where seeks are relatively expensive—the log structure may actually make reads much slower, since it [[fragmentation (computer)#External_fragmentation|fragments]] files that conventional file systems normally keep contiguous with in-place writes.
** On flash memory—where seek times are usually negligible—the log structure may not confer a worthwhile performance gain because write fragmentation has much less of an impact on write throughput{{Fact|date=November 2008}}. However many flash based devices can only write a complete block at a time because they must first perform a (slow) erase cycle before being able to write, so by putting all the writes in one block this can help performance vs writes scattered into various blocks, each one of which must be copied into a buffer, erased, and written back.
 
== References ==