On 16/11/2017, 09:17, "Osma Suominen" <[email protected]> wrote:
For TDB1 it also depends on the loading method: tdbloader2 gives
much more compact databases than tdbloader.
This is by design. As has been discussed in the past tdbloader2 produces
maximally packed B+Trees by preprocessing data which will minimise disk space
usage.
tdbloader just inserts data in the order that it in the order that it is
encountered in the inputs which likely has zero relation to the ideal data
ordering that tdbloader2 levarages.
The other key difference is that tdbloader2 is only able to create new
databases while tdbloader is able to insert into an existing database.
As Andy mentioned on an earlier thread tdb2.tdbloader essentially has the same
behaviour as tdbloader, because of the different data structures low
performance should be much better anyway and he did not think there would be
much benefit to having a tdb2.tdbloader2 variant. Also given the different Data
structures I’m not sure if this would be as practical.
Rob
