Re: Stall when committing a write transaction.

> It needs a process to reclaim old space (a GC problem) although access to > temporal versions could be considered a advantage as well. The single most important use case I have in hand would benefit enormously from this kind of persistence (although really on a transaction granularity). So at

Re: Stall when committing a write transaction.

A couple of extra data points would be useful: 1/ How large does the journal get (in bytes)? It'll go up and down in size so catching its size is tricky. 2/ Are there any readers about? They block writing the journal to the main database in addition to the QueueBatchSize Andy On 09/0

Re: Stall when committing a write transaction.

On 08/08/16 12:33, Dick Murray wrote: Hello. Looking for ideas and if anyone else has come across this... I have a bulk load (same as the previous OOME question) which auto commits after 25k quads have been added then begins a new write transaction. All of the commits average 2 seconds but one

Re: SPARQL query optimization question

Mark The key thing to understand when talking about SPARQL performance is that strictly speaking evaluation is bottom up from the leftmost child operator of the query. It is easiest to talk about these things by looking at the algebra form, for your two queries: (base