On 4.9.14 1:25 , Chetan Mehrotra wrote:
Given that such repository growth is troublesome it might be better if we configure a BlobStore by default with SegmentNodeStore (or atleast for applications like AEM). This should reduce the rate of repository growth due to
I'd leave the default as it is for Oak as this has the beauty of simplicity. We could just change it for applications where we know that the inline storing of binaries is troublesome.
OTOH in the longer term we should address the underlying issue and get compaction to work properly. If changing the default helps us with that (i.e. giving us some air to breath, gain additional information), I'm all in favour of such a move.
1. De duplication - BlobStore and DataStore (current impls) implement de duplication so adding same binary would not cause size growth 2. Lesser Fragmentation - As large binary content would not be part of data tar files Blob GC would be able to reclaim space. Currently in a cleanup if even one bulk segment in a data tar is having a reference the cleanup would not be able to remove that. That space can only be reclaimed via compaction.
Do we have enough evidence backing those claims or is this just what we would reasonable expect? I.e. if we see that such a change would reduce growth to an acceptable rate, +1. Otherwise let's gather that evidence ;-)
Michael
