Andy Seaborne wrote: > > > On 06/09/11 18:42, Sarven Capadisli wrote: >> Hi, >> >> If I use Fuseki's SOH to import my data into TDB store, tdbstats returns >> zero results for my dataset. If I use tdbloader to import my data I get >> proper results and I see a stats.opt being created inside the dataset >> directory. >> >> Is this expected behaviour? > > Yes - it's not ideal though. > > The stats file isn't maintained by the usual incremental API calls -- > only the loaders know to automatically create "stats.opt".
What would it take to update the stats incrementally as people do incremental loads and usual incremental API calls? Coincidentally, this relates to what I've just posted (without seeing this because I was writing that email). > > The original reason was that the expected usage was large(ish) initial > load and smaller incremental changes so the basic stats (and it's only > the relative numbers that matter) were still useful. that isn't always > the case, and transactions are going to make it worse. Why transactions are going to make it worse? Is it because a transaction can be aborted? Couldn't we update stats only when a transaction is successfully committed? Paolo > > What can help is to periodically run "tdbstats" on the database, and > we're in the same situation as e.g. posgresql. > > > Andy
