Re: [Virtuoso-users] Performance problems while uploading data

Hi Hugh, I haven't got the logs or core dump at hand at the moment, but it should be very easy to reproduce: just send the server a single query like "sparql insert into graph { . . . ... }", with 100,000 triples in the query. As I said, I realise this is an unreasonable thing to

Re: [Virtuoso-users] Performance problems while uploading data

Hi Jan, We are looking into these performance issue you report and shall respond back to you on them in a while. With regards to the server crash you report when performing a SPARQL insert query, was anything written to the Virtuoso Server log (virtuoso.log) at the time of the crash and w

[Virtuoso-users] Performance problems while uploading data

Hi all, I've noticed a few performance problems while using the Virtuoso JDBC driver (virtjdbc3.jar, from the Open Source release version 5.0.6) to upload triples to a Virtuoso server. First of all, I've been trying to do batch queries using Statement.addBatch() and Statement.executeBatch(). Whi

Re: [Virtuoso-users] Getting type information from SPARQL queries through JDBC interface

Sounds good, thanks. Jan 2008/6/19 Hugh Williams : > Hi Jan, > > In a way I was wonder if/when you might/would ask this question, as we hit > the same issue whilst working on our Sesame/Jena/Redland RDF Providers and > added support to the JDBC and ODBC Driver to provide this differentiation. >

Re: [Virtuoso-users] performance tuning

Hello Eric, 1. Indexes. Single bitmap index PGOS is sufficient as soon as all your queries specify graphs in use (via FROM clauses) and do not contain unbound predicates in triple patterns (even more, all predicates are constants in your samples). Other indexes are for cases of unbound P and/or