全部

1·These changes allow the kernel to avoid full timeout-based recovery scenarios under more circumstances.

这些改变允许内核在更多的情况下避免基于超时的恢复场景。

2·However, it must be taken into account what the database can handle without a transaction timeout or a transaction log full failure.

但是，必须考虑到在不出现事务超时或事务日志写满的情况下数据库能够处理的操作量。

3·For example, is the journal committed when it nears full, or through a timeout?

比如，是在日志将满时，还是在超时后？

4·Users have full control of scanning depth, maximum file size, and scan timeout.

用户对扫描深度，最大文件大小完全控制，扫描超时。