Open Freaky opened 4 years ago
Yeah, I was going to suggest this. Even without tiering an option to set this cutoff would be very useful.
@Freaky Please, take a look at adding this cutoff by modified time. Thanks.
Will be getting to it soon!
What I said but really this time.
Any chance of adding a download link for the newest development build for those comfortable with pre-releases?
What I said but really this time.
Files that get updated a lot, particularly if they're large, are poor candidates for compaction.
An obvious simple heuristic that seems likely to be relatively effective is to check file modification time, and simply have a configurable cutoff - if it's changed in the past
n
days, skip it. Tiering this by file size might also make sense - frequently decompressing and recompressing a small file is much less costly than a large one.This sort of thing will be more important should Compactor migrate to a background system service with patrol compactions.