It first invalidates the Query Cache.
它首先使查询缓存无效。
The catch, though, is that the query cache is disabled by default.
不过，问题是查询缓存在默认情况下是禁用的。
It's pointed out that a major design element for performance is the query cache.
需要指出的是关于性能的主要设计要素是查询缓存。
After you enable the query cache, it's important to understand whether it's being used effectively.
在启用查询缓存之后，重要的是要理解它是否得到了有效的使用。
MySQL has a feature called the query cache that stores the result of a query in memory, should it be needed again.
MySQL有一个特性称为查询缓存，它将（后面会用到的）查询结果保存在内存中。
Example 2: you have a "last_login" field in your table. It updates every time a user logs in to the website. But every update on a table causes the query cache for that table to be flushed.
例2：一家包括“最后登录”字段的用户表，用户每登录网站都会要更新，而每次对表的更新都会导致这个表的查询缓存要刷新。
To speed this up, you can cache the results from a search query and use these cached results whenever a user submits a query.
为了提速，您可以高速缓存从搜索查询得到的结果，然后在用户每次提交查询时使用这些缓存的结果。
Moreover, if you decided to cache based on the individual unique parts of a SOAP envelope, there is no way to indicate if the query is suitable for such caching.
此外，如果您决定在一个SOAP信封单独的、唯一的部分的基础上进行高速缓存，那么没什么办法来表明这个查询是否适于这种高速缓存。
Initial execution of any query includes the costs of building up a query cache to enable faster execution of subsequent queries.
任何一个查询的首次执行都包含了构建一个查询缓存的性能损耗，以利于提高后续查询的执行速度。
Now let us discuss the issue with the query optimization for the objects which are configured for second level cache.
现在我们来谈谈关于二级缓存的查询优化问题。
The Dynamic Query Mode must determine whether a result can be stored in the cache using a number of data points collected at runtime.
DynamicQueryMode必须确定一个结果是否可以使用在运行时收集的大量数据点存储到缓存中。
MySQL can speed the query phase using its query cache.
MySQL可以使用其查询缓存为查询阶段提速。
Nicknames do not support triggers, nor do the Materialized Query Tables (MQTs) sometimes used to cache federated data.
昵称不支持触发器，也不支持物化查询表（Materialized Query Table，MQT，有时用来缓存联邦数据）。
As a rule, if FLUSH QUERY cache takes a long time, the cache is too large.
作为一条规则，如果FLUSHQUERY CACHE占用了很长时间，那就说明缓存太大了。
SQE is the strategic query engine on DB2 for I, with better performance, scaling and tooling such as the SQL Plan Cache.
SQE是DB 2fori上的战略性查询引擎，具有更好的性能、可伸缩性和工具，例如SQLPlanCache。
Rather, the consumer only needs to query UDDI once and then can safely cache the proxy's address and use it to invoke the service repeatedly.
更确切地说，使用者只需查询uddi一次，然后就可以安全地缓存代理的地址，并且重复地使用它来调用服务。
From here on out, until the cache expires, you will be able to fetch the result array directly out of cache, skipping over the SQL query.
从这里开始，直到缓存到期，您就能够直接从缓存中获取结果数组，跳过SQL查询。
Since MQTs are local tables that cache the results of a query, the same considerations for creating an index on a local table apply to creating indexes on MQTs.
因为MQT是缓存查询结果的本地表，所以在本地表上创建索引的相同步骤也可应用于在 MQT 上创建索引。
Only if a cached copy cannot be found or has expired is the YQL query executed, and the results again are saved to the cache for future use.
仅当无法找到缓存副本或缓存副本过期时才执行YQL查询，结果再次保存到缓存以备将来使用。
The second level cache can also cache your query result.
二级缓存也能缓存查询结果。
If the cache is not complete, you need to go back to the database to perform the query instead.
如果缓存不完整，您需要返回到数据库执行查询。
The cache caches the results of any particular query for two hours.
任何查询结果都能缓存两个小时。
Once the MQT is created, it needs to be populated with data to reflect the results of the query that the MQT is supposed to cache.
一旦创建了MQT，就需要用数据填充它，以反映MQT将缓存的查询结果。
If I do not, I perform the query and store the results in the cache prior to returning the results to the Web tier.
如果未找到，则执行查询并将结果存储在缓存中，然后再将结果返回给web层。
The sequence I follow when performing reads is to take a request (that requires a database query) from the Web tier and check the cache for previously stored results of that query.
我执行读取操作的顺序是从web层获取请求(需要执行一次数据库查询)并检查之前在缓存中存储的查询结果。
Using an Ontology Web Language (OWL) defined query, you can preload the cache with regularly used queries that are made on broker startup.
使用通过本体Web语言(Ontology Web Language,OWL)定义的查询，您可以将代理启动时经常使用的查询预加载到缓存中。
Materialized Query Tables (MQTs), formerly known as Automatic Summary Tables (ASTs), can be defined to locally cache the result of queries that reference relational and non-relational nicknames.
可以通过定义物化查询表(Materialized QueryTables, MQT)——以前称为自动总结表(Automatic Summary Tables,AST)——来在本地缓存引用关系和非关系昵称的查询的结果。
In addition the Dynamic Query Mode contains a fine grained metadata and cell data cache which is trickle fed and a higher cache hit ratio than was previously possible.
此外，DynamicQueryMode包含一个细粒度元数据和单元数据缓存(即一个trickle fed)以及一个比以前更高的缓存命中率。
When compiling queries, the host server USES a feature called the object cache to accelerate query performance.
在编译查询时，主机服务器将使用称为对象缓存(object cache)的特性加速查询性能。
When compiling queries, the host server USES a feature called the object cache to accelerate query performance.
在编译查询时，主机服务器将使用称为对象缓存(object cache)的特性加速查询性能。
应用推荐