Replication Agent uses the configuration parameters scan_sleep_increment and scan_sleep_max to pause scanning when the end of the log is reached. This prevents Replication Agent from continually “spinning” on the end of the log.
By default, Replication Agent pauses up to 60 seconds before a new transaction appears because it was sleeping. When you need the maximum possible latency for a transaction to be less than the 60-second default, you can reduce the scan parameters. This results in additional CPU usage when the end of the log is reached.
Conversely, if CPU maximization is a greater concern than latency, you can increase these parameters to allow Replication Agent to use less CPU on an inactive log, at the cost of having the latency of the next transaction increased.