If applying an oplog entry requires many index writes, it can cause write conflicts (due to cache pressure) and slowness, especially as the size of the storage transaction increases. There's no need to apply the entire oplog entry in one storage transaction (we currently split up prepared transactions into multiple storage transactions, for example). I'm not sure the best way to determine when to split up a storage transaction.