Hi, >Generational garbage collection should work pretty well for this case. >If the blob store can keep track of all blobs added since revision X, >it needs to only go through the diff from that revision the latest >ones to determine which of those blobs can be removed early. > >Since most extra binaries are short-lived (temporary files, etc.), >we'd only need to do a full mark/sweep garbage collection fairly >rarely for a typical repository, like once a week or month, or perhaps >just on-demand when running out of extra space.
This could be implemented within the MicroKernel itself, without having to add an index. I added this idea to the existing issue OAK-377. Regards, Thomas
