I have a 40MB NT file that once tdb2.tdbload'ed it produces a 85MB database. Looking inside the Data-0001 directory I see many .dat and .idn files that are 8MB in size. If I remember correctly this structure is used in anticipation of future modifications of the dataset, therefore some extra space is allocated beforehand. I would like to suggest a new feature for TDB2 and tdb2.tdbloader, that is a "read-only" flag that will create the dataset (or even a single graph) assuming that it will not change in the future, and therefore optimize it for space. Or maybe a tool similar to tdb2.tdbcompact that will compact the dataset to a space-optimized read-only structure. If this is possible and if it doesn't require a complete overhaul of TDB2, it would be a really useful feature to have especially when importing 3rd-party graphs that I only need to read from, for having compact graphs/datasets.
Should I maybe open a ticket?
