Upon review, it seems that StorageInterfaceImpl::findOplogEntryLessThanOrEqualToTimestamp is primarily utilized to retrieve the optime from the oplog. In all instances where the function is used, the obtained object undergoes parsing with repl::OpTime::parseFromOplogEntry. However, the current process involves using getOwned() to acquire the oplog object to out live the local cursor, potentially resulting in a deep copy of the entire object, which may impact performance. Given that only the optime is required, I suggest revising the function's signature to handle parsing internally and return solely the optime. This adjustment aims to streamline the process and enhance performance.