另外在采集卡上还设计了数据缓存器，以实现对高速数据采集的数据传输要求。
The data buffers are integrated in the system, because of assuring data transfers of high speed data acquire.
不管是创建一个目录或文件，删除一个文件，或者是写入一个文件，元数据缓存器都要更新。
Whenever a new directory or file is created, a file is deleted, or whenever a file is written to, the metadata cache is updated.
例如，当写入一个文件的时候，这个文件的长度和最后修改时间都要在元数据缓存器里面更新。
For example, when we write to a file, the new length and the last modification timestamp are updated in the metadata cache.
元数据缓存器将目录和文件的路径名称保存为键，将元数据保存为值（如文件长度、最后修改时间、标记该条目是文件还是目录等）。
The metadata cache contains the full path names of directories and files as keys and metadata (e.g. file length, last modification date, and whether the key is a file or a directory) as values.
GridFilesystem的构造器需要传入两个Infinispan缓存器，第一个参数为数据区块缓存器(指完全创建并运行的构造)，第二个参数为元数据缓存器。
The constructor takes two (fully created and running) Infinispan caches, the first for the data chunks and the second for the metadata.
包缓存器设置数据库全局内存的总量以用于缓存程序包的静态和动态sql语句。
The package cache sets the amount of database global memory to be used for caching a package's static and dynamic SQL statements.
主要服务器将使用暂存目录中的文件，并在实际应用或暂存将保存到主要服务器的日志数据缓存之前，应立即识别对它的接收。
Primary in to files in the staging directory. It immediately acknowledges receipt of the log data buffer to the primary before it actually applies or stages it.
典型的类似流的输出方法，flush和close ，可以分别用来促使编写器将任何缓存的数据写入底层输出和关闭编写器对象。
The typical output stream-like methods, flush and close, force the writer to write any cached data to the underlying output, and close the writer object, respectively.
正如XMLStreamWriter一样，该编写器提供了flush和close方法，可分别用于将缓存数据放到底层输出和关闭编写器。
Finally, just like XMLStreamWriter, this writer provides methods flush and close to flush any cached data to the underlying output and close the writer, respectively.
这个区域使用一台远程服务器处理缓存数据。
The region USES a remote server that handles the cached data.
如果数据或指令没有出现在高速缓存中，或者如果高速缓存线路无效的时候，CPU通过从主存储器中读数据来更新它的高速缓存。
If the data or instruction is not present in the cache, or if the cache line is invalidated, the CPU updates its cache by reading the data from the main memory.
在这种情况下，即便应用程序刷新数据，也仍然会由服务器缓存，以实现优化。
In this case, even if the application flushes the data, it may still be buffered by the server for optimization.
内存影响客户端连接的数量、缓冲池的大小，以及服务器分配的数据库缓存的大小。
Memory impacts the number of client connections and the size of the buffer pool and database cache allocated by the server.
另一种重要的性能改进方法是把必需的数据缓存在接近处理器的地方。
Another important method of improving performance is through caching of necessary data close to the processor.
将工作分区与它们的数据分区进行匹配，这将增加服务器缓存的命中概率，并减少对数据库的远程访问，后者会引起较大的延迟。
Matching work partitions to their data partitions will increase the probability of a cache hit within the server and decrease remote accesses to the database, which introduces quite a bit of latency.
这是一种好的调试技巧，可以确保问题不是由于浏览器缓存中陈旧的数据造成的。
This is a good debugging technique to make sure a problem isn't resulting from stale data in the browser cache.
这是用于同时管理本地缓存的数据和来自服务器的实时数据的典型代码。
This is all typical code for managing both locally cached data, and live data from the servers.
如果用户键入相同的关键词两次，由于浏览器缓存的缘故，实际上仅进行一个请求，因为第二次发出请求时浏览器返回缓存的数据。
If the user types in the same term twice, because of the browser cache only one request is actually made because the second time it's requested the browser returns the cached data.
动态缓存可以利用应用服务器中的DRS在集群的各个服务器中复制缓存的数据。
Dynamic cache can take advantages of DRS in the application server to replicate cached data across servers in a cluster.
为了提高应用程序的性能，数据库中的数据被缓存在应用服务器中。
To improve application performance, the data in the database is cached in the application server.
但大多数数据响应均已指明不存储在浏览器的缓存之内。
Most data responses, however, are already specified to not be stored within the browser cache.
持续查询使得客户端应用能注册对移动存储在缓存服务器集群上的数据的查询。
Continuous querying enables client applications to register queries to express complex interest on moving data stored in the cache server cluster.
这台远程缓存服务器可以被多个JCS客户端应用程序用于存储缓存数据。
The remote cached server can be used by multiple JCS client applications to store the cached data.
为了避免缓存过期，元数据服务器将收回不准确的布局。
To prevent stale caches, the metadata server recalls layouts that have become inaccurate.
但是，我们控制所有类型的缓存器，数据分布缓存器、字典缓存器、SPL例程缓存器和sql语句缓存器。
But we do have control on all kinds of cache, Data-distribution cache, Dictionary cache, SPL routine cache, and SQL statement cache.
由于附加元数据不能直接提交到服务器，它被缓存在客户端直到服务器可再次连接。
As the additional metadata cannot be submitted directly to the server, it is cached in the client until the server is reachable again.
下面的场景可能会用无效的数据“毒害”边缘服务器缓存。
Following is a scenario that can potentially "poison" the edge server cache with invalid data.
例如，假设一个任务正在CPU - 1上执行，其数据在这个处理器的缓存中。
For example, suppose a task executed on CPU-1, and its data was in that processor's cache.
要计算数据访问时间，您需要了解数据存在于近缓存中、服务器缓存中、以及数据库中的概率。
To compute the data access time, you need to know the probabilities for the data existing in the near-cache, in the server cache, and in the database.
管理代理缓存arm数据，并将其发送到管理服务器。
The management agent caches the ARM data and sends it to the management server.
应用推荐