Hi, If the tar file only contains a few entries, then I think it's not a problem. If the tar file contains many entries, then I think this by itself is an issue, as maintaining such an index is problematic.
I would prefer if the smallest entry is 10 KB, which would result in less entries, and reading the index should be faster. Some statistics about segement sizes based on one example repository: total size: 1'218'330'536 bytes (5 tar files) average size: 27'630 bytes total count: 44'093 entries count, segement size between 17681, 10-99 6269, 100-999 11397, 1000-9999 4554, 10000-99999 8746, 100000-999999 4192, 1000000-9999999 Regards, Thomas On 14/02/14 14:42, "Axel Hanikel" <[email protected]> wrote: >Hi, > >The org.apache.jackrabbit.oak.plugins.segment.file.TarFile constructor >reads through the whole tar file, building up an in-memory map from >segment uuid to the position in the file. This is done each time the >repository is started, and it takes quite a long time. Shouldn't this >index be persisted somehow, and be updated when the tar file is being >written to? > >Should I create an issue for this or am I missing anything? > >Bye! > Axel > >
