| jorlow@chromium.org | 179be58 | 2011-03-18 22:37:00 +0000 | [diff] [blame] | 1 | ss |
| 2 | - Stats |
| jorlow@chromium.org | 179be58 | 2011-03-18 22:37:00 +0000 | [diff] [blame] | 3 | |
| 4 | db |
| 5 | - Maybe implement DB::BulkDeleteForRange(start_key, end_key) |
| 6 | that would blow away files whose ranges are entirely contained |
| 7 | within [start_key..end_key]? For Chrome, deletion of obsolete |
| 8 | object stores, etc. can be done in the background anyway, so |
| 9 | probably not that important. |
| dgrogan@chromium.org | 29c68f1 | 2012-10-12 19:13:17 +0000 | [diff] [blame] | 10 | - There have been requests for MultiGet. |
| jorlow@chromium.org | 179be58 | 2011-03-18 22:37:00 +0000 | [diff] [blame] | 11 | |
| gabor@google.com | 8cd4ab8 | 2011-06-22 02:36:45 +0000 | [diff] [blame] | 12 | After a range is completely deleted, what gets rid of the |
| 13 | corresponding files if we do no future changes to that range. Make |
| 14 | the conditions for triggering compactions fire in more situations? |