The second level cache can also cache your query result.
二级缓存也能缓存查询结果。
Now let us discuss the issue with the query optimization for the objects which are configured for second level cache.
现在我们来谈谈关于二级缓存的查询优化问题。
This provides a method of securing many web service solutions; an object level cache lets you do it all quickly and easily.
这提供了一个使许多Web服务解决方案安全的方法；一个对象级别的高速缓存能使您迅速且简单地完成。
You might also be able to use approaches like a two-level cache to improve both the remote cache hit rate and the retrieval rate.
您可能还能够使用二级缓存等方法同时提高远缓存访问率和检索率。
This leads to various inefficiencies, especially loss of low-level cache contents when moving to a new processor with a cold cache.
这会导致多种效率低下，尤其是当低级缓存内容迁移到具有冷缓存的新处理器时会丢失低级缓存内容。
Most caches are implemented using the Singleton pattern involving a static reference to a top level cache class as shown in this example.
使用Singleton模式实现的大多数缓存都涉及本例所示的对顶级cache类的静态引用。
If a distributed cache is desired, we recommend using one of the WebSphere-provided distributed cache implementations. These can be used as a second level cache with hibernate.
如果需要分布式缓存，我们建议使用WebSphere提供的分布式缓存实现之一。
Generally, it does this by maintaining awareness or state of the mapped entity class instances it is responsible for by keeping a first-level cache of instances, valid for a single thread.
通常，它通过保留对单个线程有效的一级缓存实例，维护它负责的映射实体类实例的可识别性或状态，从而做到这一点。
If we try to eager fetch the department entity then for every fetch of same department the database is hit for department information even though it is available in our second level cache.
如果对department实体采取预先抓取，那么对于同样的department实例，纵使它位于二级缓存中，每次也都需要查询数据库。
It USES the J2EE architecture to cache objects and results at every level.
它使用J2EE体系结构在每一个级别缓存对象和结果。
With this command, you can dump the cache contents to a file, display statistics of cache usage, flush the cache table, and change the logging level of the daemon.
使用这个命令，您可以将缓存的内容转储到文件中、显示缓存使用情况的统计信息、刷新缓存表，以及更改该守护进程的日志级别。
We looked at techniques not only at the PHP level, by leveraging an opcode cache and optimizing the PHP configuration, but also looked at optimizing your database design for proper indexing.
我们不仅通过利用一个操作码缓存和优化PHP配置探究了php级别的技术，而且探究了如何优化您的数据库设计来实现合理的索引编制。
This means the browser can't distinguish between news item 1 and news item 2 and therefore cannot cache on the browser level.
这意味着浏览器不能分辨新闻1和新闻2，因此也不能在浏览器上缓存。
They can also enable or disable GZIP compression and set the level of cache cleanout.
他们还可以启用或禁用GZIP压缩，并设置缓存清除的级别。
It is not easy to monitor these caches with a standard installation, and many times you rely on turning on the correct logging level to see how a specific cache is being used.
对于标准安装，要监视这些缓存并不容易，并且在许多时候，您将依赖于启用适当级别的日志记录才能确定特定缓存的使用情况。
The cache level management includes the information generated by individual cache instances.
缓存器级别的管理包含了每个缓存器实例生成的信息。
One of the ways that you can fine tune performance is to adjust the level of cache scrubbing.
更好地调优性能的一个方法是，调整缓存清除的级别。
Level 1 cache commonly supports single-cycle access.
一级缓存通常支持单周期访问。
Each processor also has its own fast memory (a level 1 cache).
每个处理器也拥有自身的快速内存(1级缓存)。
Level 2 cache supports two-cycle access.
二级缓存支持两周期访问。
When you define a WebSphere eXtreme Scale cache, you specify the level of replication by specifying the number of replica shards.
定义WebSphereeXtremeScale缓存时，您通过指定复制碎片（replica shard）缓存指定复制水平。
After turning on Hibernate's log level to trace, we found it was the updating of session cache that caused the delay.
将Hibernate的日志级别调成trace后，我们发现是更新会话缓存造成了延时。
Beginning with Lotus Domino 6.5, administrators can set the level of cache cleanout by defining which elements (style sheets, static code, Web pages, URLs, and so on) to keep in the cache.
在开始使用LotusDomino 6.5时，管理员可以通过定义在缓存中保存哪些元素(样式表、静态代码、web页面、URL等)来设置缓存清除的接别。
By default, class caches are created with user-level security, so only the user that created the cache can access it.
在默认情况下，以用户级安全性创建类缓存，所以只有创建这个缓存的用户才能访问它。
However, regardless of the access level used, a cache can only be destroyed by the user that created it or by the root user.
但是，不管使用什么访问级别，只有创建缓存的用户或根用户能够销毁缓存。
A singleton service locator with a resource cache creates a global cache that cannot properly handle the component-level mappings for an overloaded resource name.
带有资源缓存的集合服务定位器创建全局缓存，通过这种方式不能为重载的资源名正确处理组件级映射。
The additional CPUs, amount of level two cache, and memory provided better capacity and response time at specific user loads.
额外的CPU、二级缓存量和内存，在特定用户负载下可提供更好的容量和响应时间。
Cache can be configured on the controller level, and ultimately USES the ASP.NET caching infrastructure.
缓存能在控制器级别配置，最终是利用了ASP.NET的缓存基础功能。
You will find that we page cache four of the six top level menu choices.
您会发现我们会页面缓存六个顶端菜单中的四个。
For example, it doesn't have session cache, and nor does it interact with any second-level or query cache.
例如，它不需要会话缓存，也不和任何二级缓存或查询缓存有交互。
应用推荐