Currently the applier must (sequentially) do the following in a loop:
- batch oplog entries
- apply and record in local oplog
- journal, including minvalid
The task here is to break the last two steps (journal + reporting) into a separate process which doesn't block the next batch from starting/applying. This should allow higher throughput on the replicas without adversely affecting latency.