Inotifywatch - gather filesystem access statistics using inotify.
Inotifywatch -使用inotify来统计文件系统访问信息。
The charging part includes the flow statistics and service access statistics.
计费部分包括流量统计和按访问业务统计。
Jeff Goldberg’s informative rant on why you shouldn’t rely on access statistics and hit counters.
JeffGoldberg内容丰富的演说告诉你为什么不应该过度依赖访问统计和计数器；
For example, Web-access statistics (as currently compiled) are little more than frequency counts grouped in various ways.
例如，Web访问统计信息(按当前所编辑的)只不过是以各种方式进行分组的频率计数。
Background management component include: library management, order management, membership management, security management, web site management and access statistics.
后台管理部分包括：图书管理、订单管理、会员管理、安全管理、网站管理和访问统计等。
It estimates the execution cost of each potential access plan based on the statistics data stored in catalog and statistics tables, and selects the one with the lowest cost.
它会基于存储在目录和统计表中的统计数据而评估每一个可能的存取计划的执行开销，然后选择最低开销的存取计划。
After you collect those statistics, you get the new access plan graph shown in Figure 10.
您收集了这些统计数据之后，会得到如图10所示的新访问计划图。
Runtime statistics can also be gathered for access plan operators during the execution of a section.
访问计划操作者也可以在一个片段执行时收集运行时统计信息。
You can obtain the statistics from the table descriptor of the table node in the underlying access path graph.
您可以从基础访问路径图中的表节点的表描述符处获得该统计信息。
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.
这种比较的结果可能会指向一些过时的统计信息—例如，优化器用来选择一个错误访问计划的统计信息。
With JOPR, administrators have access to graphical views of key run-time parameters or statistics and can also be notified if these exceed or go below certain limits.
使用JOPR，管理员可以用可视化的方式访问一些重要的运行时参数或统计数据，同时也可以得知这些参数和统计数据是否超标或过低。
First analyze the access plan that the optimizer chooses when no distribution statistics are available, which is only basic statistics for the table CARS, and that its indexes exist.
首先来分析一下，在没有分布统计信息，而只有cars表的基本统计信息及其索引的情况下，优化器选择的访问计划是怎样的。
The DB2 optimizer USES these statistics to determine the most efficient access plan for any given query, which improves query performance.
DB 2优化器使用这些统计信息为任何给定的查询决定最有效的访问计划，从而提高查询的性能。
Insufficient or inaccurate statistics lead to inaccurate cost estimates for the candidate access paths and is the most common reason for the selection of inefficient access paths.
不充分或不准确的统计数据会导致对候选访问路径评估不准确，这也是选择低效访问路径的最常见原因。
The costs for this access plan are clearly below the costs for the access plan without distribution statistics: 203.809, instead of 3242.63.
这个访问计划的成本明显低于没有分布统计信息时的成本：前者为203.809，而后者为3242.63。
Although the access plan is better than the access plan with concrete values without distribution statistics, it is worse than the access plan with concrete values with distribution statistics.
虽然这个访问计划比使用具体值但没有分布统计信息情况下的访问计划好，但不如既使用具体值又有分布统计信息时的访问计划。
The query access plan produced after collecting these statistics is the same as the final plan in Example 3.
收集这些统计信息后生成的查询访问计划与示例3中的最后的计划相同。
The inconsistent statistics may also mislead the optimizer into choosing a bad access path.
不一致的统计数据还会误导优化器选择糟糕的访问路径。
As you've seen in the steps above, the optimizer selects the optimal access plan based on available statistics.
您可以从以上步骤看到，这个优化器基于可用的统计信息选择了最优的存取计划。
Even if the number of rows in a table remains consistent, changes in data contents can result in different, and hopefully better, access paths using statistics updated by RUNSTATS.
即使表的行数保持一致，使用由RUNSTATS更新的统计信息来更改数据内容可以产生不同的、也许更好的访问路径。
The DB2 optimizer USES catalog statistics to determine the best access path, and the main method employed to update these catalog statistics is to run the RUNSTATS utility.
DB 2优化器使用目录统计信息来确定最佳的访问路径，而更新这些目录统计信息所采用的主要方法就是运行RUNSTATS实用程序。
DB2 and IDS USES the statistics information in the catalog table to derive the best access plan.
DB2和IDS使用目录表中的统计信息来制定最佳访问计划。
Rebind applications that use static SQL after using RUNSTATS so that the query optimizer can choose the best access plan given the new statistics.
在使用RUNSTATS之后需要重新绑定使用静态SQL的应用程序，这样查询优化器就可以选择新统计信息所给出的最佳存取方案。
If current statistics are not available, the optimizer may choose an inefficient access plan based on inaccurate default statistics.
如果无法获得当前的统计数据，优化器就可能会基于不准确的默认统计数据选择低效的访问计划。
There is an attribute RUNSTATS TIMESTAMP on the table or index node of the access plan graph that indicates the last time when the statistics were collected.
在访问计划图的表或索引节点上会有一个RUNSTATSTIMESTAMP属性，它表示收集统计数据的时间。
The parameter ALLOW read access in a RUNSTATS command specifies that other users can have read-only access to the table while statistics are calculated.
在RUNSTATS命令中的参数ALLOWREADACCESS指定计算统计信息时，其他用户可以只读地访问该表。
LIisting 5: Statistics class defining access methods.
清单5：定义访问方法的statistics类。
Develop a servlet to access Place Statistics feeds.
开发一个servlet来访问PlaceStatistics提要。
Select a query and click Tune to transfer the query to IBM Data Studio to format the query, analyze the access plan, or check whether statistics are current and optimal.
选择一个查询并单击Tune 可将其转化为IBMDataStudio，来格式化查询、分析访问计划、或者检查统计是否存在且最优。
My second performance tip is to use the new integrated platform statistics for the access and analysis of operating system and Domino statistics.
我的第二个性能技巧是，在访问和分析操作系统和Domino统计数据时，使用最新的集成平台统计数据。
应用推荐