更好的性能指示器是GC的速率，因为即使您对不具备相同时间的日志进行比较，它仍然非常有意义。
An even better indicator is the rate of GC, as it is still meaningful even if you're comparing logs that do not cover the same amount of time.
通过检查日志语句的执行时间来查明存储过程的性能问题。
To pinpoint performance problems in the stored procedures by examining execution times of the logging statements.
CLOSE_LOG会在最后向日志中写入最后一条消息，内容是从启动日志到结束日志经过了多少时间。
The CLOSE_LOG writes the last message with the elapsed time from start of the logging to the end of the logging.
当超过为发送日志指定的最小等待时间间隔之后，将重新尝试发送。
Retry attempts are made after the minimum time interval specified for sending logs.
OAT提供DBA所需的大量信息，比如磁盘空间使用情况、日志文件、消耗IO时间最多的sql语句、最慢的sql语句等等。
The OAT provides the much needed information required by the DBA like the disk space usage, log files, SQL statements occupying the most IO time, the slowest SQL statements, and so on.
换句话说，无法前滚到上次全数据库备份以来的任意时间点或日志的末尾。
In other words, you cannot roll forward to a specific point in time or to the end of logs from the last full database backup.
如果你已经试验过列表中的其他贴士了，又想要在将来提高自己时间管理的能力，那么试试记时间日志。
If you've tried out the other tips on this list and you want to improve your time management even further, then try keeping a time log.
所有日志记录都为日志增加了日期和时间戳；但是，插件的责任是在日志中确认本身，因为合并文件中写入了多个插件。
All logging adds a date and time stamp to the log; however, it is the plug-in's responsibility to identify itself in the log due to the multiple of plug-ins writing to the combined file.
很显然小组自已开发的日志框架(像所有日志框架一样)随着时间而增大。
It became evident that the team's home-grown logging framework (like all logging frameworks) had grown over time.
利用在线备份，就可以将日志前滚到任何特定的时间点或日志的末尾。
With online backup, there is a means to roll forward the logs to any specific point in time or to the end of the logs.
日志里只要体现日期、时间、你的锻炼情况仅此而已。
如果应用程序的性能从整体上来看比较差，那么应激活日志记录功能来通过日志消息时间戳识别发生问题的位置。
If your application performs poorly in general, activate logging to try to identify problem areas through log message timestamps.
清单2的输出显示了一个大写的、带时间戳的日志消息
The output from Listing 2 shows a log message with a time stamp in uppercase
在测试脚本中生成记录时间的日志。
对stop方法的调用记录了执行时间并打印日志信息。
The call to the stop method records the execution time and prints a log message.
Normalize复选框确定是使用相对于日志(规范)开始的时间还是使用绝对时间(非规范)。
The normalize check box determines whether The Times are shown relative to the start of the log (normalized) or in absolute time (unnormalized).
时间日志是一个记录你正在做什么的简单记录。
A time log is simply a record of what you're doing when. It might look like.
Logging——如果时间允许，我们会将日志api加到GWT 2.1中。
Logging - The logging API may make it into GWT 2.1 if time permits.
LastFilled列显示最后一次使用每个逻辑日志的日期和时间。
The Last Filled column informs the user of the date and time when each logical log was used for the last time.
从DB 2写一条日志记录，到QCapture读这条日志记录，这之间经历的时间就是日志延时。
The time between when DB2 writes a log record and QCapture reads it is the log latency.
我迅速地写了一个基于PHP的东西，摘录了“SessionStart”和“SessionClose”（会议开始/结束）的标记和那些日志的时间印记，然后把它们全转成一张图。
I quickly wrote a PHP script that extracts the Session Start and Sessions Close markers and timestamps from these logs and transfers them into an image.
消息窗口构件，显示已记录日志的时间戳记数。
A message widget that shows the number of timestamps that have been logged.
这些日志文件随着时间会不断增大，所以不应该长时间启用该设置，否则会消耗掉所有可用的设备空间。
These log files grow in size over time, so you should not leave this setting enabled for long periods or you could consume all available drive space.
理解这一点最好的办法就是记录下网站和访问站点的时间日志，并追踪看起来效果最好的设计模式。
The best way to understand this is to log time on the web, visiting sites and keeping track of the design elements that seem to work best.
备份索引告诉它要保留日志多长时间，因此在到达最大尺寸时，该日志将被重命名，一个全新的日志文件又开始了。
The backup index tells it how many old logs to retain, so when the maximum is reached the log is renamed and a fresh new one started.
如果有必要确定服务器范围内事件的完整时间线，则可以根据每个日志中与各项关联的时间戳将日志合并在一起。
If it is necessary to determine a complete timeline of events server-wide, the logs can be merged based on the timestamps associated with each entry in each log.
如果要对不同的机器记录日志，那就必须对这些机器的时间戳进行同步，否则日志消息的次序就混乱了。
If logging is performed on different machines, the machines' timestamps must be synchronized, or the log messages will be out of order.
日志必须包含时间戳，其中含有时区，精确到毫秒或纳秒。
Logs must contain timestamps, with timezone, to the millisecond or nanosecond.
这对于短时间运行非常方便，但对于涉及较长时间段的日志不太理想。
This is convenient for short runs, but not so ideal for logs covering longer time periods.
即使有些端口现在没有使用，审计子系统可以用来查找已经使用了哪些端口(在审计日志文件记录的时间范围内)。
The audit subsystem can be used to find out which ports have been used (for the duration of the audit log files) even if they are not currently in use.
应用推荐