The IBM XL C compiler is a very good optimizer, and as a result, the C algorithm delivers superior results to a simple unoptimized assembly language implementation.
IBMXLC编译器是一个非常好的优化器，结果是 C算法的性能要比未经优化的汇编语言实现的性能好很多。
This is already a good value because it guarantees that the optimizer, by using the quantile statistics, only has an estimated maximum error of 5% for the determined filter factors.
这已经是一个较好的值，因为它可以保证优化器在使用分位数统计信息的情况下对确定过滤因子的估计误差最大只有5%。
The query optimizer might come up with a different query execution plan tailored to provide good performance for fast retrieval of first 'n' rows rather than all the result rows.
查询优化器可能得出一个不同的查询执行计划，这个计划可以专门为最快地获取前'N '行，而不是所有结果行提供良好的性能。
At times, semantically equivalent code, written in two different ways, might cause the optimizer to have a more difficult time performing good register allocation.
有时，语义上等同但采用两种不同方式编写的代码可能会使优化器在执行良好的寄存器分配上所花费的时间相差巨大。
Now the optimizer should have a good starting point. Enable 'use control points of:' for the nadir image, enable Viewpoint optimization for the nadir image, and optimize again.
现在优化器应该有一个良好的起点。启用“使用控制点：'低潮的图像，使图像的角度优化的最低点，和再优化。”
After each modification, start from step 1 mentioned above, until the optimizer reports a good result.
每次改动后，从步骤1所述的开始，直到优化器报告一个好的结果。
If the optimizer reports a good or 'not bad' result, it has probably found the right position of the nadir image.
如果优化器报告好或不好的结果，它可能已经找到了正确的位置的图像的最低点。
It is still a good idea to keep in mind since not all opcode optimizers perform this optimization and there are plenty of ISPs and servers running without an opcode optimizer.
牢记这个优化处理不失为一个好主意，因为并不是所有的指令优化器都会做同样的优化处理，并且存在大量没有装配指令优化器的互联网服务提供商(ISPs)和服务器。
It is still a good idea to keep in mind since not all opcode optimizers perform this optimization and there are plenty of ISPs and servers running without an opcode optimizer.
牢记这个优化处理不失为一个好主意，因为并不是所有的指令优化器都会做同样的优化处理，并且存在大量没有装配指令优化器的互联网服务提供商(ISPs)和服务器。
应用推荐