This setting controls the size of the file system cache.
该设置控制文件系统的缓存大小。
NET program at login time that gets the assemblies loaded into the file system cache.
净程序在登录时获取程序集加载到文件系统缓存。
So the file system cache can help there quite a bit to avoid read and write operations on the disk.
所以文件系统缓存可以很大程度上帮助避免对磁盘的读写操作。
For DMS device container tablespaces, the operating system does not cache pages in the file system cache.
对于DMS设备容器表空间,操作系统不在文件系统缓存器中缓存页面。
In a well-tuned site, this disk offload file fits entirely into the file system cache, and is served out of RAM.
在一个优化的网站上,这个磁盘卸载文件会完全存储在文件系统缓存中,它位于RAM之外。
These elements are stored in the browser's file system cache so that the browser needs to download them over the network only once.
这些元素存储在浏览器的文件系统缓存中,因此,浏览器只需要通过网络下载一次这些元素即可。
As described earlier, Domino Web Access caches many of the external references, such as UI design elements, in the browser's file system cache.
正如前面所描述的,在浏览器的文件系统缓存中,DominoWebAccess缓存了许多外部引用,比如UI设计元素。
It is important to note that file system caching was disabled by specifying the no file system CACHE clause when each table space in the database was created.
重要的是,要注意当每一个数据库表空间创建时,文件系统缓存已经通过指定NOFILE SYSTEM cache子句并被禁用。
When set to 0 ( Default ) a standard sized file system cache is allocated (Less than 10MB RAM); this is recommended as it provides best Application performance.
当设置为0(默认)标准大小的文件系统缓存分配(少于10MB的内存),这是推荐的。
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.
现在,对于一般的数据库操作,不必考虑文件系统缓存,因为DB 2实现了缓冲池,这些缓冲池已经做了必要的缓存。
Simplified tuning and operational maintenance due to the fact that with eXtreme Scale, you do not need to worry about tuning the size of the disk offload file or file system cache performance.
由于使用了eXtremeScale,简化了调优和操作维护,您不需要为调优磁盘负载文件的大小或文件系统缓存性能而担忧。
The rationale is this: access to a file system based container goes through the operating system kernel, and the operating system comes with a file system cache to speed up repetitive access to files.
理由是:对基于容器的文件系统的访问要经过操作系统内核,而操作系统带有一个文件系统缓存,可以加快对文件的重复访问。
Further, applications that might benefit from having a file system read ahead or high buffer cache hit rates might actually see performance degradation.
而且,对于那些受益于文件系统预读功能或者较高缓冲区缓存命中率的应用程序,可能会出现性能的降低。
If you enable disk offload, the entry that would be removed from the cache is copied to the local file system.
如果您启用磁盘卸载,则要从缓存中删除的条目将复制到本地文件系统。
The file server process sends the file to the client cache with a callback attached to it so that the system can deal with any changes happening somewhere else.
文件服务器进程把文件发送到客户机缓存内并随其附带一个回调,以便系统可以处理发生在其他地方的任何更改。
The difference between these two is a result of the drive cache and can have implications for the file system journal.
这两种定义是由于磁盘缓存而存在而产生的,对文件系统的日志有重大影响。
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).
文件系统层之下是缓冲区缓存,它为文件系统层提供了一个通用函数集(与具体文件系统无关)。
When the cache manager reconnects to the central servers, the system reintegrates the client modification log, making all file system updates available to the client.
当缓存管理器与中央服务器重新连接时,系统重建客户机修改日志,使所有的文件系统更新对客户机都可用。
Linux, under normal circumstances, USES a system file cache to buffer, read, and write requests from disk.
在一般情况下,Linux使用一个文件系统缓存为磁盘请求进行缓冲和读写。
Use GPFS pagepool to cache user data and file system metadata.
使用GPFSpagepool 可以缓存用户数据和文件系统元数据。
Prior to the Linux 2.6 kernel, file caching on a Linux system could go awry, using a huge number of cycles trying to manage the file cache.
对于Linux 2.6之前版本的内核,Linux系统上的文件缓存可能会出差错,需要花费大量的周期来管理文件缓存。
Helper objects include the cache manager (the cache object) and the internal file system monitor used to detect changes in the source files that form the application.
帮助对象包括缓存管理(Cache对象)和用于发现应用程序源文件改变的内部文件系统监控器。
The Cache Manager can respond to requests from a local application to fetch a file from across the AFS file system.
CacheManager可以响应本地应用程序的请求,来跨AFS文件系统取出文件。
This is useful in a file cache management system.
这是非常有用的文件缓存管理系统。
Perhaps your code needs to cache user Settings or a temporary data file but the default security cannot allow network-deployed code to access the general file system.
可能您的代码需要缓存用户的设置或者一个临时数据文件,但是默认的安全性与允许网络部署代码访问这个文件系统。
This removes the schema from the in-memory schema cache, but not from the file system.
该操作将从内存中的架构缓存中移除架构,但不从文件系统中移除架构。
File cache - Even with the PHP opcode cache enabled, the PHP engine has to accesses the script files on a file system.
文件缓存-即使启用了PHP操作码缓存,PHP引擎要访问一个文件系统上的脚本文件。
If a cache file exists, it is sent directly to the browser, bypassing the normal system execution.
如果存在缓存文件,将直接输出到浏览器,不用走下面正常的系统流程;
For example, instead of using the default in-memory cache engine, you can create custom providers that store cache data in databases, in custom objects, or in the file system.
例如,与其使用预设的记忆体中快取引擎,您可以建立将快取资料储存在资料库、自订物件或档案系统中的自订提供者。
By default, the service providers will use the local file system for the cache.
根据预设,服务提供者将使用本机档案系统来进行快取。
应用推荐