以最近使用(LRU)列表的形式管理缓冲区缓存。
The buffer cache is managed as a set of least recently used (LRU) lists.
缓冲区缓存会缓存文件系统和相关块设备之间的请求。
The buffer cache buffers requests between the file systems and the block devices that they manipulate.
该缓冲区缓存原本需要从磁盘读取的JMS消息数据。
This buffer caches JMS message data that may otherwise need to be read from disk.
缓冲区缓存——为存储从物理数据文件读取的数据块而分配的内存。
Buffer Cache - Memory allocated for storing data blocks read from physical data files.
缓冲区缓存为存储从物理数据文件读取的数据块而分配的内存。
Buffer Cache Memory allocated for storing data blocks read from physical data files.
传输、访问和缓存(内核块缓冲区缓存)命中率的缓冲区活动。
Buffer activity for transfers, accesses, and cache (kernel block buffer cache) hit ratios.
例如，对底层设备驱动程序的读写请求会通过缓冲区缓存来传递。
For example, read and write requests to the underlying device drivers migrate through the buffer cache.
缓冲区缓存之下是设备驱动程序，它实现了特定物理设备的接口。
Below the buffer cache are the device drivers, which implement the interface for the particular physical device.
将磁盘的数据复制到缓冲区缓存，然后再复制文件数据时会出现多余的副本。
This copy occurs when the disk is copied to the buffer cache and then again from the file.
文件系统层之下是缓冲区缓存，它为文件系统层提供了一个通用函数集(与具体文件系统无关)。
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).
而且，对于那些受益于文件系统预读功能或者较高缓冲区缓存命中率的应用程序，可能会出现性能的降低。
Further, applications that might benefit from having a file system read ahead or high buffer cache hit rates might actually see performance degradation.
大多数文件系统都通过缓冲区缓存来相互通信，这种缓存通过缓存最近使用的数据来优化对物理设备的访问。
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.
可以通过设置postgresql . conf文件中的shared _ buffers参数来更新缓冲区缓存。
Buffer cache can be updated by setting the shared_buffers parameter in the postgresql.conf file.
注意，可以使用sync命令将缓冲区缓存中的请求发送到存储媒体(迫使所有未写的数据发送到设备驱动程序，进而发送到存储设备)。
Note that you can use the sync command to flush the buffer cache out to the storage media (force all unwritten data out to the device drivers and, subsequently, to the storage device).
biod守护进程提高了整体NFS性能，因为它可以充当与客户端应用程序之间的中间环节，既可以清空缓冲区缓存，也可以填满缓冲区缓存。
The biod daemon improves overall NFS performance as it either empties or fills up the buffer cache, acting as a liaison of the client applications.
当创建表空间时，可以将它与特定的缓冲区池(数据库缓存)关联起来，并关联到特定的容器。
When you create a table space, you can associate it with a specific buffer pool (database cache) as well as to specific containers.
数据的丢失可能造成数据库负荷过多，因为缓存不再充当数据子集的缓冲区。
The loss of this data might cause the database to become overloaded, as the cache is no longer acting as a buffer for that subset of the data.
通过使用一个软引用来管理高速缓存的缓冲区，可以解决LeakyChecksum中的问题，如清单2所示。
We can fix the problems in LeakyChecksum by using a soft reference to manage the cached buffer, as shown in Listing 2.
初始化slab分配器并为VFS、缓冲区高速缓存等创建slab高速缓存。
Initializing the slab allocator and creating slab caches for VFS, buffer cache, etc.
可以使用lvmo修改每个卷组的pbuf(即固定内存缓冲区)，可以显示和控制用来缓存卷组数据的内存。
Lvmo allows you to change the pbuf, or pinned memory buffers, used for each volume group, and therefore shows and allows control over the memory used to cache volume group data.
包与目录缓存，以及工作空间（如包高速缓冲区命中率）。
Package and catalog caches, and workspaces (for example, package cache hit ratio)
下一行告诉我们尽管有 231MB 内存正在使用，但是应用程序只使用了其中的 86MB；缓冲区和高速缓存使用了其余的内存。
The next line shows us that while 231MB is being used, only 86MB of this is actually being used by applications; the rest is being used for buffers and cache.
要设置大小适当的目录缓存器、包缓存器和日志缓冲区以提高性能。
Set the catalog cache, package cache, and log buffer size to an appropriate size to improve performance.
缓存中缓存最近使用的缓冲区(页面)，这些缓冲区可以快速提供给各个文件系统。
Instead, the most-recently used buffers (pages) are cached here and can be quickly provided back to the individual file systems.
然而，可用内存统计可能是不可靠的，因为操作系统使用了很多动态缓冲区和缓存。
However, the free memory statistic is likely to be unreliable since the OS USES a lot of dynamic buffers and caches.
DB 2和Oracle数据库都提供了允许将数据表数据缓存在RAM中的缓冲区。
Both DB2 and Oracle databases provide buffers that allow table data to be cached in and served from RAM.
目录缓存器、包缓存器和日志缓冲区。
在读取方面使用中间内核缓冲区，可以允许内核缓冲区在应用程序不需要内核缓冲区内的全部数据时，充当 “预读高速缓存（readahead cache）” 的角色。
Using the intermediate buffer on the read side allows the kernel buffer to act as a "readahead cache" when the application hasn't asked for as much data as the kernel buffer holds.
mytop还提供了一个有关关键字缓冲区和查询缓存效率的实时数据和历史数据，以及有关正在运行的查询的统计信息。
mytop also provides real-time and historical data about key-buffer and query-cache efficiency, and statistics about the queries being run.
因为从逻辑上划分内存缓冲区或高速缓存内存和固件的内存。
Because memory logically divided on buffer or cache memory and firmware memory.
应用推荐