Write-through, write-around and write-back cache
来源:互联网 发布:文件夹恢复软件 编辑:程序博客网 时间:2024/06/01 07:35
Write-through, write-around and write-back cache
There are three main caching techniques that can be deployed, each with their own pros and cons.
Write-through cache directs write I/O onto cache and through to underlying permanent storage before confirming I/O completion to the host. This ensures data updates are safely stored on, for example, a shared storage array, but has the disadvantage that I/O still experiences latency based on writing to that storage. Write-through cache is good for applications that write and then re-read data frequently as data is stored in cache and results in low read latency.
Write-around cache is a similar technique to write-through cache, but write I/O is written directly to permanent storage, bypassing the cache. This can reduce the cache being flooded with write I/O that will not subsequently be re-read, but has the disadvantage is that a read request for recently written data will create a “cache miss” and have to be read from slower bulk storage and experience higher latency.
Write-back cache is where write I/O is directed to cache and completion is immediately confirmed to the host. This results in low latency and high throughput for write-intensive applications, but there is data availability exposure risk because the only copy of the written data is in cache. As we will discuss later, suppliers have added resiliency with products that duplicate writes. Users need to consider whether write-back cache solutions offer enough protection as data is exposed until it is staged to external storage. Write-back cache is the best performing solution for mixed workloads as both read and write I/O have similar response time levels.
There are three main caching techniques that can be deployed, each with their own pros and cons.
Write-through cache directs write I/O onto cache and through to underlying permanent storage before confirming I/O completion to the host. This ensures data updates are safely stored on, for example, a shared storage array, but has the disadvantage that I/O still experiences latency based on writing to that storage. Write-through cache is good for applications that write and then re-read data frequently as data is stored in cache and results in low read latency.
Write-around cache is a similar technique to write-through cache, but write I/O is written directly to permanent storage, bypassing the cache. This can reduce the cache being flooded with write I/O that will not subsequently be re-read, but has the disadvantage is that a read request for recently written data will create a “cache miss” and have to be read from slower bulk storage and experience higher latency.
Write-back cache is where write I/O is directed to cache and completion is immediately confirmed to the host. This results in low latency and high throughput for write-intensive applications, but there is data availability exposure risk because the only copy of the written data is in cache. As we will discuss later, suppliers have added resiliency with products that duplicate writes. Users need to consider whether write-back cache solutions offer enough protection as data is exposed until it is staged to external storage. Write-back cache is the best performing solution for mixed workloads as both read and write I/O have similar response time levels.
0 0
- Write-through, write-around and write-back cache
- The Difference between write through and write back for cache
- Cache 的write back和write through
- Cache 中 Write through/Write back 区别
- Cache 的write back和write through
- Cache之write back与write through
- Cache 的write back和write through
- Cache 的write back和write-through
- Cache 的write back和write through
- Cache 的write back和write through
- Cache 的write back和write through
- Cache 的write back和write through
- Cache 的write back和write through
- Cache 的write back和write through
- Cache 的write back和write through
- Cache 的write back和write through
- cache的write through和write back
- write back和write through
- HTTP服务端接口模拟工具-HttpServerMockTool
- iOS代码实现常用控件之Slider 文字缩放
- spring+springmvc+mybatis详细运转流程
- FlycoDialog_Master--对话框
- 转:关于A类,B类,C类IP地址的网段和主机数的计算方法
- Write-through, write-around and write-back cache
- 跨域问题:No 'Access-Control-Allow-Origin' header is present on the requested resource.
- Linux中Tomcat的安装和配置方法
- Dom节点对象转化为字符串
- [IOS 开发] XML解析
- Golang初级系列教程-继承和子类
- Android中WebView和JavaScript(JS)的互相调用
- 如何生成HTMLTestRunner报告
- c1TrueDBGrid 常用属性