Currently, deleting documents in '_cappedDeleteAsNeeded' happens in one transaction. As a result of SERVER-1864, this could be costly in the case where the newly set cappedSize decreases past the collections current size.

SERVER-1864 holds off on deleting documents until the next insert into the collection. After inserting, we check if deletions are needed and delete documents until the total size < cappedSize in one transaction.