Ideally, there should be no Log pages read.
理想情况下，应该没有日志页面读。
Increase the size of the log buffer area if there is considerable read activity on a dedicated log disk, or there is high disk utilization.
如果在某个专用的日志磁盘上存在大量的读活动，或者具有较高的磁盘利用率，就增加日志缓冲区域的大小。
Thus, the read operations compete with log writing and the write operation for data pages from the buffer pool.
因而，读操作与日志写和缓冲池中的数据页的写操作之间存在竞争。
I'll walk you through the process of downloading and using the ECS libraries to develop a sample application that can read various log files and generate a status report in HTML format from them.
我将带您完成下载并使用ecs库开发一个示例应用程序的过程，这个应用程序可以读取不同的日志文件，并用它们生成html格式的状态报告。
It includes the ability to read test logs created from the testing tool and to create test log results for the configured test case.
它包括阅读测试工具创建的测试日志的能力，以及为已配置测试用例创建测试日志结果的能力。
Although the first two command types perform no action within the kernel, the rest are used to read log messages or control aspects of logging.
虽然前面两个命令类型不会对内核进行任何操作，但是其余命令则是用于读取日志消息或控制日志。
Though this file is relatively simple, longer log files can be very complex and cumbersome to read and analyse.
这个文件相对简单，但是长的日志文件会非常复杂并难于阅读和分析。
If you see a large number of LOG pages read, it indicates that the value of the LOGBUFSZ database parameter should be increased.
如果看到了较多数目的日志页面读，就表示应该增加LOGBUFSZ数据库参数的值。
The next step is to read and parse the log files to gather the information you need.
下一步是读取并解析日志文件以收集所需要的信息。
Here, logging output influences other parts of a system in terms of business relevance, in other words, other applications read business critical log records and use those in their business logic.
在这种情形下，根据业务的相关程度，日志的输出将影响到系统的其它部分，换句话说，其它应用程序将读取关键业务日志并应用到它们的商业逻辑中。
Three commands are used to read log messages.
其中有三个命令是用于读取日志消息的。
Instead of paying for costly subscriptions, log on and read online.
用上网阅读新闻来代替昂贵的订阅费。
The ratio of the number of Log pages read to the number of Log pages written should be as small as possible.
日志页面读数目与日志页面写数目的比值应尽可能小。
When a log full condition is encountered, read access is still allowed on the database.
当遇到日志写满情况，仍允许对数据库的读访问。
When you run queries for very large audit log tables, you can end up with a situation where your database system has to read thousands of pages into the bufferpool to compute the result.
当您在大型审核日志表格中运行查询功能时，您可能会在您的数据库系统不得不向缓冲池读入数千页面以进行计算时而结束。
This helps me to identify straight away, when viewing the audit log or the audit report, if there has been a read or write access on the file.
这有助于在查看审计日志或审计报告时明确区分读访问和写访问。
The pre-loading was incorporated as part of the load testing, which was set up to read a list of all of the HKEYs and log each user into the portal once.
预装载被合并为装载测试的一部分，它设计用来一次读取保存所有HKEY 的列表并将每个用户记录到门户。
MyProgress is billed as the world's first online application "designed to helping an individual [not a corporate] manage their progress and read their life log as an RSS feed."
MyProgress被记录为世界上第一个“旨在帮助个人[而不是公司]管理自己的进步和通过rss聚合来阅读人生日志”的在线应用。
However, if you were to use something like the NotSupported transaction attribute instead, it would cause the database query to read from the table, not the transaction log.
但是，如果您使用的是NotSupported事务属性，那么它会造成数据库查询从表中而不是从事务日志中读取数据。
A better approach is to let the Twisted server itself hold a file handle for the log file, and only read new records when needed.
更好的办法是让t wisted服务器自己拥有一个针对日志文件的文件句柄，只在需要时才读取新记录。
This is the time it takes QCapture to read the update from the log and write it to the WebSphere MQ queue.
这是QCapture从日志读取更新和将更新写到WebSphereMQ队列所花的时间。
If you need to read the contents of a file backwards (for instance, to analyze a log in reverse order), use the CPAN module file: : ReadBackwards.
如果您要从尾到头读取文件的内容(例如，为了分析日期从近到远排列的日志记录)，那么使用CPAN模块File： ReadBackwards。
Log pages read is the number of log pages read from disk by the logger, while log pages written is the number of log pages written to disk by the logger.
日志页面读(logpagesread)是日志记录器(logger)从磁盘读取的日志页面的数目，而日志页面写(log pages written)是日志记录器(logger)写入磁盘的日志页面的数目。
This file is then sent back to the client with write, the log file is generated with another write, and the server performs a final read from the browser.
然后使用write将这个文件发送回客户端，使用另一个write生成日志文件，并且服务器执行来自浏览器的最后一个read。
TPC-C is an OLTP benchmark which requires efficient use of large memory, intensive random read/write I/O, and has extremely intensive database log activity.
TPC-C是一种OLTP基准，要求有效地使用大量内存，大量的随机read/writeI/O，并且有很密集的数据库日志活动。
This is commonly read by a daemon (klogd or rsyslogd) that consumes the messages and passes them to rsyslog for routing to the appropriate log file (based on its configuration).
这个读取操作通常是由一个守护程序(klogd或rsyslogd)实现的，它会处理这些消息，然后将它们传递给rsyslog，以便(基于它的配置)转发到正确的日志文件中。
Many WebSphere Application Server processes need read access to numerous files and write access to the log and transaction directories.
许多WebSphereApplicationServer进程都需要对无数文件具有读访问权限，并且对log和transaction目录具有写访问权限。
Most optimizations, checkpoint processing (aggregating intermediate results so that recovery actions never need to read the entire log), and "fringe cases" are beyond our scope.
大多数的最优化技术，检查点处理(聚集中间结果以便不需要读整个日志就可以恢复动作)和“边缘案例”超出了我们的范围。
The transaction log is stored as a sequential disk file (or sometimes in a raw partition) and will generally only be written to, not read from, except in the case of rollback or recovery.
事务日志存储为连续的磁盘文件(有时存储在原始分区中)，并且一般只是用于写入而不用于读取，回滚或恢复的情况例外。
That means that other applications read business critical log records and use them for their business logic.
其它应用程序将读取关键业务日志并应用到它们的商业逻辑中。
应用推荐