Therefore, it is useful to get the data only once, cache it, and have all other components use the cached data, instead of accessing the backend system again.
因此，只一次获取数据，对数据进行缓存，并让所有其他组件使用该缓存的数据，而非再次访问后端系统，这是很有益的。
If the memory cache is used only for performance reasons, then storing data in memory cache might not be such a big problem.
如果只是由于性能方面的原因而使用内存缓存，则在内存缓存中存储数据可能不会是个大问题。
The challenge for portal frameworks is to only cache the fragment without any dependencies on artifacts outside of the fragment.
门户框架所面临的挑战是只缓存片段，而不缓存片段以外的构件上的任何依赖项。
If all the data fits in the cache, then the data is read from disk only once; after that, all requests are satisfied from the cache at memory speed.
如果所有数据都在缓存中，那么只需从磁盘读取一次数据；毕竟，所有的请求都可以用内存速度从缓存中得到满足。
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.
如果用户键入相同的关键词两次，由于浏览器缓存的缘故，实际上仅进行一个请求，因为第二次发出请求时浏览器返回缓存的数据。
Each instance has to initialize its own cache, but it only caches the references it USES, and is able to access the reference directly rather than having to look it up in a hash map.
每个实例必须初始化其自身的缓存，但它只缓存那些它要使用的引用，并且可以直接访问引用而不是要到一个散列映射中去寻找。
It is reset only by a missing cache file or replication interval setback.
仅在缺少缓存文件或复制间隔出现错误时重新设置它。
By default only file cache pages are loaned.
在默认情况下，只借出文件缓存页面。
By default, we will only cache tuples potentially smaller than 150,000.
默认情况下，我们将仅可能缓存少于150,000的元组。
However, regardless of the access level used, a cache can only be destroyed by the user that created it or by the root user.
但是，不管使用什么访问级别，只有创建缓存的用户或根用户能够销毁缓存。
Please note this only affects data cache (tuple storage) and not metadata cache.
请注意这只会影响数据缓存（元组存储）且没有元数据缓存。
Cache doesn't really help if you only read items once.
如果您只需读取这些条目一次，那么缓存实际上帮助不大。
As will be discussed later, the application talks only to the cache, and the cache talks to the disk.
我们将在下文介绍，应用程序仅与缓存对话，缓存则与磁盘对话。
Only the code creating the cache object needs to know about the new kind of cache.
只有创建缓存对象的代码需要了解新的缓存类型。
The sparse cache only stores a subset of the data and can be populated lazily.
稀疏缓存仅存储数据的子集，可以被延迟填充。
Cache tables are similar to MQTs with the restriction that a cache table supports only non-aggregate queries over a single table.
缓存表类似于具有以下限制的MQT，即缓存表只支持单个表上的非聚集查询。
The near cache is also only useful if it has a large enough capacity to obtain a high hit rate.
近缓存也只有在它含有大量足够空间可用的时候才有用。
The field cache has therefore been modified such that it only reloads parts where the segment has changed.
因此，修改后的字段缓存只会加载更新过的片断。
If the client invokes any operation that updates a record from the preferred source (it has a valid id and is in the cache), the operation may only provide partial information.
如果客户端调用任何用于更新来自首选源的记录(它具有有效的ID并且在缓存中)的操作，那么该操作可能仅提供部分信息。
Our cache is only useful if it is accurate, so we need to make sure that it is in sync with our server.
必须确保缓存是准确的，因此需要确保它与服务器同步。
The when_fragment_expired method will execute only when the associated cache fragment expires.
when _ fragment_expired方法只有在相关的缓存分段过期时才会执行。
While each of the above computations are cached by Fabric in typical usage, only the cache pertaining to the first computation invocation context is currently able to be distributed.
虽然Fabric在典型使用中缓存上述每个计算结果，但是目前只能分布与第一个计算调用上下文相关的缓存。
If you used the mechanism above, the portlet would always return the same content during the cache time, and the content would only be updated whenever the cache data expires.
如果您使用上面的机制，该portlet在缓存时间内将一直返回相同的内容。该内容只有在缓存数据过期的时候才会被更新。
By default, this cache goes back only seven days.
默认情况下，这个缓存只能保存7天以内的记录。
ZumoDrive keeps a cache of files on your hard drive, but that is only a cache and doesn't necessarily contain all of your files.
ZumoDrive在用户硬盘上保留了文件缓存，而不是用户的所有文件。
The HTML file with the reference to the manifest is automatically included in the application cache. The manifest contains only the following.
引用清单的HTML文件自动包含在应用程序缓存中。
If you do not have an overall cache policy design, it can not only give you bad performance, but can also invoke some functional defects.
如果您没有一个整体缓存策略设计，那么您的缓存策略不仅会导致低劣的性能，还会引发一些功能缺陷。
By default, class caches are created with user-level security, so only the user that created the cache can access it.
在默认情况下，以用户级安全性创建类缓存，所以只有创建这个缓存的用户才能访问它。
When a program writes to memory, the processor only modifies the line in the cache, but does not update main memory.
当一个程序写入存储，处理器仅仅只会修改缓存线，而不会更新主要的存储内容。
When offline, it can only access offline resources in the cache manifest.
离线时，它只能访问缓存清单中的离线资源。
应用推荐