ivandika3 commented on PR #10876: URL: https://github.com/apache/ozone/pull/10876#issuecomment-5128676308
> KforceOptimized potentially reduces writeAmplifications by ensuring the files which were newly generated in the compaction doesn't get redundantly get compacted again. Ok, sounds valid. > Let us go through an example of an iterator. Thanks for the explanation. I see the benefit of deleteRange if most a lot of large ranges are covered by deleteRange. > With the proposed changes we would not have a lot of tombstones to begin with and only multiple range tombstones which would not be in big numbers thus the iterator overhead would be minimal not as major as you would think This might not be assumed, if user sends a lot of delete requests, tombstones might still be a lot. Also for existing cluster which high tombstones, the overhead still happens. @swamirishi Btw, please help to approve this if you think it looks good so I can merge it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
