Flash Caching on the Storage Client

View/ Open
Published Version
http://0b4af6cdc2f0c5998459-c0245c5c937c5dedcca3f1764ecc9b2f.r43.cf2.rackcdn.com/11792-atc13-full_proceedings.pdfhttp://0b4af6cdc2f0c5998459-c0245c5c937c5dedcca3f1764ecc9b2f.r43.cf2.rackcdn.com/11743-atc13-holland.pdf
Metadata
Show full item recordCitation
David A. Holland, Elaine Angelino, Gideon Wald, Margo I. Seltzer. 2013. Flash Caching on the Storage Client. In Proceedings of the 2013 Usenix Annual Technical Conference, San Jose, CA, June 26-28, 2013.Abstract
Flash memory has recently become popular as a caching medium. Most uses to date are on the storage server side. We investigate a different structure: flash as a cache on the client side of a networked storage environment. We use trace-driven simulation to explore the design space. We consider a wide range of configurations and policies to determine the potential client-side caches might offer and how best to arrange them. Our results show that the flash cache writeback policy does not significantly affect performance. Write-through is sufficient; this greatly simplifies cache consistency handling. We also find that the chief benefit of the flash cache is its size, not its persistence. Cache persistence offers additional performance benefits at system restart at essentially no runtime cost. Finally, for some workloads a large flash cache allows using miniscule amounts of RAM for file caching (e.g., 256 KB) leaving more memory available for application use.Terms of Use
This article is made available under the terms and conditions applicable to Open Access Policy Articles, as set forth at http://nrs.harvard.edu/urn-3:HUL.InstRepos:dash.current.terms-of-use#OAPCitable link to this page
http://nrs.harvard.edu/urn-3:HUL.InstRepos:11324016
Collections
- FAS Scholarly Articles [18153]
Contact administrator regarding this item (to report mistakes or request changes)