Read-only batches (BatchRequest.IsReadOnly) execute directly upon a *RocksDB which bypasses the optimization to reuse iterators across execution of a command that occurs when using a *rocksDBBatch. We could create a rocksDBReadOnly engine which performed similar iterator reuse without creating an associated batch for writes. Or, we could change *rocksDBBatch to only create the C++ batch when the first mutation occurs.