What is a "write-behind" cache?
什么是“write - behind”缓存？
Listing 1. An example of write-behind configuration.
write - behind配置的示例。
This daemon is required to perform both read-ahead and write-behind requests.
执行预读和后写请求都需要用到该守护进程。
Either a sparse cache or complete cache could be used with the write-behind feature.
稀疏的缓存还是完整的缓存，都可以用于write - behind特性。
These benefits and its simple configuration make the write-behind caching a truly powerful feature.
这些优势以及它配置的简单性，都使得write - behind缓存异常的强大。
This means the write-behind cache must reliably keep the data in the cache until it can be written to disk.
这意味着写入后缓存必须可靠地在缓存中保存数据，直到写入磁盘位置。
The database CPU utilization charts illustrate the improvement in back-end load when using write-behind.
数据库的CPU占用率图表展现了使用write - behind对后端加载的改善。
They can also provide scalable servicing of update requests by leveraging their write-behind technology.
通过使用write - behind技术，这些产品还提供更新请求的可伸缩服务。
In the write-behind case, transactions no longer have to wait for the database write operation to finish.
使用write-behind，不再要求事务等待数据库的写操作完成。
In a write-behind cache, once the data is in the cache, the request is returned, and processing continues.
在write - behindcache模式下，当数据位于缓存中时，请求将返回，并且处理继续进行。
Listing 4 shows the response times for the write-behind scenario where all transactions are committed to the grid.
列表4展示了write - behind场景下的响应时间，在这种情况下所有的事务都被提交到网格中。
We ran the sample code using write-through and write-behind for a comparison in response time and database CPU utilization.
我们分别使用了write -through和write - behind技术运行示例代码，比较了各自的响应时间以及数据库的CPU占用率。
As discussed earlier, with a write-behind cache, the transaction completes when the data is written to the cache, which is fast.
正如上文讨论的一样，使用写入后缓存，事务在数据写入缓存时完成，这样速度更快。
The write-behind function batches updates to the back-end database asynchronously within a user configurable interval of time.
write - behind功能能够根据用户配置的间隔时间，异步地对后端数据库进行批量更新。
This article reviewed the write-behind caching scenario and showed how this feature is implemented with WebSphere eXtreme Scale.
本文重新审视了write - behind缓存技术，并展示了如何在WebSphereeXtreme Scale下实现这一特性。
The new system writes profile changes to the grid and then these changes are pushed to the database using the write-behind technology.
新的系统则是将个人信息的变更写入到网格中，然后使用write-behind技术将这些变更推到数据库中。
The write-behind caching feature, supported as part of the new Ehcache API, works with asynchronous batching of updates to the database.
后写式缓存特性作为新ehcacheAPI的一部分，适用于对数据库的异步批量更新。
The sample code includes a client driver that mimics operations on the grid to demonstrate how the write-behind caching function increases performance.
示例代码包含一个客户端驱动器，模仿在网格上的操作，用以演示write-behind缓存功能如何提高性能。
Thus, a write-behind cache gives you memory speed for accessing data on all writes, and for all cache-hit reads, and has other benefits that you will see later.
因此，write - behind缓存在访问所有写入数据以及所有缓存命中读取时都能提供内存速度，而且还有一些其他好处，我们将在下文介绍。
In a write-behind cache, data reads and updates are all serviced by the cache, but unlike a write-through cache, updates are not immediately propagated to the data store.
在write - behind缓存中，数据的读取和更新通过缓存进行，与write -through缓存不同，更新的数据并不会立即传到数据库。
In this paper, we will illustrate how to optimize the performance of an application by leveraging the write-behind pattern with examples using IBM WebSphere eXtreme Scale.
本文将使用IBMWebSphereeXtreme Scale演示如何利用write - behind模式优化应用程序的性能。
The write-behind configuration should be tuned to best match your environment with regards to the ratio of write transactions, the same record update frequency, and database update latency.
write - behind的配置可以调整，以满足自己的运行环境，这其中包括写事务的比例，相同记录更新的频率，以及数据库的更新延迟。
The two charts demonstrate how the write-through scenario results in higher response times for updates whereas the write-behind scenario has update times that are nearly the same as the reads.
这两个图表极为明显地说明，对于更新而言，write -through响应时间更长，而write - behind耗费的更新时间几乎与读取操作相同。
This write-behind delayed-write has several advantages, even beyond the increased response time for the user on writes. The back-end database itself can be greatly offloaded and used more efficiently.
这种写入后延迟写入有几个好处，不仅仅是增加了用户对写入的响应时间。
Some writers cannot produce a word unless they are poised behind a desk, while others prefer to write sitting outdoors or in noisy restaurants.
有些作家只有坐在桌子后面才能写出东西，而另一些作家则喜欢坐在户外或嘈杂的餐馆里写作。
Today, Chinese people still use these fans, only not many people write or paint on them anymore. Next time when you are waving a fan, you may think of the stories behind it.
今天，中国人仍然使用这些扇子，只是不再有很多人在上面写字或画画了。下次当你挥舞扇子的时候，你可能会想起它背后的故事。
Indeed, one of the reasons behind the 2022 date for "recommendation" status is the need to write full test suites.
的确，2022这个到达“建议”状态的日期背后的其中一个原因就是需要编写完全测试包。
The three partners arranged an amicable split, and in late 1996, Allen and Kathryn founded their company in the cottage behind their house, where he hunkered down to write his book.
随后1996晚些时候，艾伦和凯瑟琳创立了自己的公司，公司就设在他们房子后面的小别墅里。艾伦开始潜心写作。
With random write behind, the number of pages in memory exceeds a specified amount and all subsequent pages are written to disk.
使用延迟的随机写操作，当内存中的页面数量超过指定的数量，则将所有后续的页面写入到磁盘。
One of the ideas behind GWT is that you can write your code using software engineering best practices.
GWT背后的一个理念是支持使用软件工程最佳实践来编写代码。
应用推荐