该文介绍使用缓冲文件系统处理工程应用中的大量数据，及日常生活的二维表管理。
Use the buffer file system to process lots of data of project and table management.
日志文件系统是使用日志来缓冲文件系统的修改(同时也可以应用于紧急故障恢复)的，但可以根据记录的时间与内容采取不同的策略。
Journaling file systems use a journal to buffer changes to the file system (which is also used in crash recovery) but can use different strategies for when and what is journaled.
现在，对于一般的数据库操作，不必考虑文件系统缓存，因为DB 2实现了缓冲池，这些缓冲池已经做了必要的缓存。
Now, for normal database operation you do not really have to worry about the file system cache because DB2 implements buffer pools that do the necessary caching already.
通常，熟文件更慢，因为存在附加的开销和文件系统提供的缓冲。
In general, cooked files are slower because of the additional overhead and buffering provided by the file system.
文件系统层之下是缓冲区缓存，它为文件系统层提供了一个通用函数集(与具体文件系统无关)。
Below the file system layer is the buffer cache, which provides a common set of functions to the file system layer (independent of any particular file system).
在没有文件系统缓存的情况下，xml列在db2缓冲池进行缓冲而clob列则不是，从而可降低开销。
Without file system caching, this overhead is mitigated by the fact that XML columns are buffered in the DB2 buffer pool and CLOB columns are not.
所谓日志就是一种特殊的文件，它会在一个循环的缓冲区内记录文件系统的修改，然后将其定期提交到文件系统。
The journal is a special file that logs the changes destined for the file system in a circular buffer. At periodic intervals, the journal is committed to the file system.
大多数文件系统都通过缓冲区缓存来相互通信，这种缓存通过缓存最近使用的数据来优化对物理设备的访问。
Most of the file systems communicate through a buffer cache, which is a cache that optimizes access to the physical devices by caching recently touched data.
而且，对于那些受益于文件系统预读功能或者较高缓冲区缓存命中率的应用程序，可能会出现性能的降低。
Further, applications that might benefit from having a file system read ahead or high buffer cache hit rates might actually see performance degradation.
缓冲区缓存会缓存文件系统和相关块设备之间的请求。
The buffer cache buffers requests between the file systems and the block devices that they manipulate.
缓存中缓存最近使用的缓冲区(页面)，这些缓冲区可以快速提供给各个文件系统。
Instead, the most-recently used buffers (pages) are cached here and can be quickly provided back to the individual file systems.
在没有文件系统缓存的情况下，XML和clob列的Q1执行效果类似，不在缓冲池进行缓冲的clob列略微落后(10%)。
Without file system caching, Q1 performs similarly on XML and CLOB columns, with a slight disadvantage (10%) for the CLOB column which is not buffered in the buffer pool.
而直接I/O 可以避免使用文件系统缓冲区，因而对于磁盘的读写更为高效。
Direct I/O bypasses the use of the file system buffers, and therefore is more efficient for reads and writes that go to disk.
Sendfile(2)是一种避免缓冲区复制开销的技术，并且它直接将数据位从文件系统转移到网络。
Sendfile (2) is a technique that avoids buffer copy overhead, and it directly pushes bits from the file system onto the network.
在一般情况下，Linux使用一个文件系统缓存为磁盘请求进行缓冲和读写。
Linux, under normal circumstances, USES a system file cache to buffer, read, and write requests from disk.
数据层—文件系统|数据库|缓冲系统。
当Linux关闭时，它仔细地把所有的缓冲区数据转送到磁盘，并确保文件系统被彻底卸载，以保证系统再次启动时能够使用。
When Linux shuts down, it carefully flushes all cached data to disk and ensures that the filesystem is cleanly unmounted, so that it's ready for use when the system starts up again.
缓冲器被收集成簇，簇被收集成卷，而一个单一的HAMMER文件系统可以跨多个卷。
Buffers are collected into clusters, cluster are collected into volumes, and a single HAMMER filesystem may span multiple volumes.
缓冲器被收集成簇，簇被收集成卷，而一个单一的HAMMER文件系统可以跨多个卷。
Buffers are collected into clusters, cluster are collected into volumes, and a single HAMMER filesystem may span multiple volumes.
应用推荐