Re: [Virtuoso-users] Ubuntu upgrading

2016-09-12 Thread Pantelis Natsiavas
Thank you Hugh. I have removed the old virtuoso.trx file and everything seems in place. Kind regards, Pantelis Natsiavas 2016-09-08 4:47 GMT+03:00 Hugh Williams : > Hi Pantelis, > > The "It is impossible to have a database file > /media/VirtuosoDBDrive/virtuoso.db > with a length not multiple

Re: [Virtuoso-users] Timeout when listing graphs

2016-09-12 Thread Pantelis Natsiavas
Hi Hugh. I had changed the virtuoso.ini vector parameters in the past due to working with large datasets. One of these changes could have caused the problem. However, I can not confidently say which. I have changed the parameters you suggested, however, still I cannot get an answer to the graphs q

Re: [Virtuoso-users] Out of curiosity, some questions about OpenSource Virtuoso settings

2016-09-12 Thread Hugh Williams
Hi Lorenz, In Virtuoso 7+ Vectored query execution [1] enables single, typically complex analytical types queries, to be broken down and executed on multiple threads. The INI file param that controls this is “ThreadsPerQuery” [2] , which controls the maximum number of threads that can be claim

Re: [Virtuoso-users] Timeout when listing graphs

2016-09-12 Thread Kingsley Idehen
On 9/12/16 3:50 AM, Pantelis Natsiavas wrote: > SPARQL SELECT distinct ?graph WHERE { GRAPH ?graph { ?s ?p ?o } }; Please try: SPARQL SELECT distinct ?graph WHERE { GRAPH ?graph { ?s a ?o } }; -- Regards, Kingsley Idehen Founder & CEO OpenLink Software (Home Page: http://www.openlink

Re: [Virtuoso-users] Out of curiosity, some questions about OpenSource Virtuoso settings

2016-09-12 Thread Davis, Daniel (NIH/NLM) [C]
Tangentially on JDBC/ODBC vs HTTP.HTTP is slow because of the transport, but JDBC/ODBC has more mature models of paging over results, pre-fetching, etc. I feel that RDF is mature as a Data format, but as a protocol it is not that mature. -Original Message- From: Hugh Williams [mai

Re: [Virtuoso-users] Out of curiosity, some questions about OpenSource Virtuoso settings

2016-09-12 Thread Paul Houle
The trouble with classic http is that pretty frequently you wind up making a separate TCP connection for each API call. In theory there was pipelining in http/1.1 but it did not really work and was rarely implemented in "web service" scenarios. http/2 has pipelining that works, reduces the # of