optimizer
n. [计] 优化程序;最优控制器
2026-04-13 22:10 浏览次数 16
n. [计] 优化程序;最优控制器
1. to make as perfect, effective, or functional as possible
optimize energy use optimize your computer for speed and memory
— Charles Brannon
2. to make (something) as good or as effective as possible
optimization program优化程序
Image Optimizer图像优化;图片压缩工具(软件名)
Code Optimizer代码优化器
File Optimizer文件批量压缩工具
Sys Optimizer系统优化精灵
Circuit Optimizer电路优化
optimizer boot默认只启用优化启动
Business Optimizer业务优化模块
Budget Optimizer预算优化工具
FSOFreeStyle Optimizer自由风格曲面优化
the db2 optimizer then queries system information and statistics stored in the db2 system catalog to determine the best method of accomplishing the tasks necessary to satisfy the sql request.
db2优化器然后查询存储在db2系统目录中的系统信息和统计信息,以确定完成满足sql请求所必需的任务的最佳方法。
if the value is set to 0, then the optimizer chooses index scans over table scans if appropriate indexes exist, without even considering the estimated costs.
如果将其值设置为0,那么当存在合适的索引时,优化器就选择索引扫描而非表扫描,甚至不考虑估算成本。
an entry is added to the system catalog to indicate to the query optimizer that such a remote index exists.
一个条目被添加到系统编目中,以向查询优化器表明存在那样的一个远程索引。
with three predicates applied in the where clause, assuming they are independent results in the optimizer underestimating the cardinality.
在where子句中应用了三个谓词,如果假设它们是独立的话,会导致优化器低估基数。
cardinality estimation is a process by which the optimizer uses statistics to determine the size of partial query results after predicates are applied or aggregation is performed.
基数估计是这样一种过程:在应用了谓词或执行了聚集之后,优化器使用统计信息确定部分查询结果的大小。
by default, the optimizer considers this type of scan.
默认情况下,优化器考虑这种类型的扫描。
tuning such an environment by only analyzing the optimizer plans is not feasible due to the quantity of produced plans.
由于所产生的计划数量太多,仅通过分析优化器计划来调优该环境是不可行的。
in this case, the optimizer assumes an even distribution of all values in column_y, which means it assumes that all values have the same frequency.
在这种情况下,优化器认为所有值在 column_y 中是平均分布的,这意味着它认为所有的值都有相同的出现频率。
once you understand your options, you can influence the optimizer to select the best query execution plan, either by adjusting the optcompind parameter or by adding query directives or indexes.
一旦理解了自己的选择,就可以通过调整optcompind参数,或者通过添加查询指示或索引,来影响优化器,从而选择最佳的查询执行计划。
however, in the absence of data distribution information, the optimizer will calculate selectivity for filters of different types based on table indexes.
然而在缺乏数据分布信息的情况下,优化器将基于表索引计算不同类型筛选器的选择性。
the result of this comparison can potentially point to out-of-date statistics — for example, used by the optimizer to select an incorrect access plan.
这种比较的结果可能会指向一些过时的统计信息 —例如,优化器用来选择一个错误访问计划的统计信息。
the db2 optimizer uses these characteristics and restrictions when determining the best way to process a query.
db2优化程序使用这些特征和限制来确定处理一个查询的最佳方法。
pda tells the query optimizer whether an operation can be performed at a remote data source.
pda告诉查询优化器一个操作是否可以在某个远程数据源上执行。
when no warning message or diagnostic message is issued, it indicates that the optimizer has applied the guideline.
如果没有出现任何警告信息或诊断消息,那么表明优化器已经成功应用了準则。
at each operator in the access plan, the optimizer estimates the cardinality output from the operator.
对于访问计划的每个操作符,优化器将估计该操作符的基数输出。
the optimizer calculates and compares the costs of each join method and selects the best one to use when evaluating query execution plans.
当评估查询执行计划时,优化器计算并比较每种连接方法的成本,然后选择要使用的最佳方法。
this command updates the statistics in the system catalogs that the optimizer uses to determine the lowest-cost query plan.
此命令更新了系统目录中的统计数据,优化程序使用这些数据来确定成本最低的查询计划。
with this feature, the query optimizer can immediately consider the index when determining an access plan.
有了这个特性,查询优化器可以在决定访问计划时立即考虑索引。
this set is input to the cost-based optimizer that decides whether to use any of the eligible indexes or not.
将该组索引输入到基于成本的优化器,这个优化器决定是否使用任何合适的索引。
by inlining method calls, not only is the method call overhead eliminated, but it gives the optimizer a larger basic block to optimize, with substantial opportunity for dead-code optimizations.
通过内联方法调用,不仅方法调用的开支被清除,而且给优化器提供了更大的优化块可以优化,会带来相当大的死代码优化机会。
you can leverage the extended use of multi-column statistics in db2 9.5 to provide the optimizer more information to better estimate the cardinality in order to choose an optimal query access plan.
您可以利用db29.5 中的多列统计信息的扩展用途来为优化器提供更多的信息,从而使优化器更好地估计基数,选择最佳的查询访问计划。
in this case, the optimizer uses a generic rule or a default value to estimate an average cost by assuming normal data distribution.
在这种情况下,优化器会使用一个通用规则或者默认值以正常数据分布率来评估得到一个平均开销值。
another way to influence the optimizer is to use query directives.
影响优化器的另一种方式就是使用查询命令。
in this scenario, after analysis, it was determined that it will be optimum to use the index i11 to access the table tab1, but the default behaviour of the optimizer did not, even after tuning.
在这个场景中,经过分析,可以确定使用索引i11来访问表tab1是最优的,但是优化器的默认行为不会这么做,即使在调优之后也仍然不会这样做。
the optimizer uses system catalogs indicating how many rows there are and how well the indexes are formed to figure out what query path to use.
优化程序采用系统目录,说明那里有多少行,以及构造了较好的索引来计算所采用的查询路径。