169c6d383S[email protected]ss 269c6d383S[email protected]- Stats 369c6d383S[email protected] 469c6d383S[email protected]db 569c6d383S[email protected]- Maybe implement DB::BulkDeleteForRange(start_key, end_key) 669c6d383S[email protected] that would blow away files whose ranges are entirely contained 769c6d383S[email protected] within [start_key..end_key]? For Chrome, deletion of obsolete 869c6d383S[email protected] object stores, etc. can be done in the background anyway, so 969c6d383S[email protected] probably not that important. 10*946e5b5aSDavid Grogan- There have been requests for MultiGet. 1169c6d383S[email protected] 12ccf0fcd5S[email protected]After a range is completely deleted, what gets rid of the 13ccf0fcd5S[email protected]corresponding files if we do no future changes to that range. Make 14ccf0fcd5S[email protected]the conditions for triggering compactions fire in more situations? 15