Even persisting the same data with no change to the data causes the memory to increase.
On Thu, Feb 12, 2015 at 9:45 AM, Trevor Donaldson <[email protected]> wrote: > @Rob, > > So if I am processing 1000+ triples every 15 minutes with some updates > (delete triple / insert new triple) should I persist the model at the end > and not try to persist every 100 or so? Would this fix the size issue? It > seems as though the size grows when I persist every 100 using putModel vs > persisting at the end. > > On Thu, Feb 12, 2015 at 9:35 AM, Damian Steer <[email protected]> wrote: > >> On 12/02/15 13:49, Trevor Donaldson wrote: >> >> On Thu, Feb 12, 2015 at 6:32 AM, Trevor Donaldson <[email protected] >> > >> >> wrote: >> >> >> >>> Hi, >> >>> >> >>> I am in the middle of updating our store from RDB to TDB. I have >> noticed >> >>> a significant size increase in the amount of storage needed. >> Currently RDB >> >>> is able to hold all the data I need (4 third party services and 4 >> years of >> >>> their data) and it equals ~ 12G. I started inserting data from 1 third >> >>> party service, only 4 months of their data into TDB and the TDB >> database >> >>> size has already reached 15G. Is this behavior expected? >> >> Hi Trevor, >> >> How are you measuring the space used? TDB files tend to be sparse, so >> the disk use reported can be unreliable. Example from my system: >> >> 6.2M [...] 264M [...] GOSP.dat >> >> The first number (6.2M) is essentially the disk space taken, the second >> (264M!) is the 'length' of the file. >> >> Damian >> >> -- >> Damian Steer >> Senior Technical Researcher >> Research IT >> +44 (0) 117 928 7057 >> > >
