Hi Thomas, Can you please set the following INI file params in the “[Parameters]” section, restart Virtuoso and rerun the queries to see if the response time for the second query and DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS() improves :
VectorSize = 1000 AdjustVectorSize = 0 Best Regards Hugh Williams Professional Services OpenLink Software, Inc. // http://www.openlinksw.com/ Weblog -- http://www.openlinksw.com/blogs/ LinkedIn -- http://www.linkedin.com/company/openlink-software/ Twitter -- http://twitter.com/OpenLink Google+ -- http://plus.google.com/100570109519069333827/ Facebook -- http://www.facebook.com/OpenLinkSoftware Universal Data Access, Integration, and Management Technology Providers > On 5 Apr 2016, at 10:24, Thomas Michaux <mich...@abes.fr> wrote: > > Hello, > > I found strange that V7.2.2 is faster to answer : > > > SQL> sparql SELECT ?g COUNT(*) AS ?c { GRAPH ?g {?s ?p ?o.} } GROUP BY ?g > ORDER BY DESC(?c); > 37 Rows. -- 2447 msec. > (use all 8 cores and CPU up to 800%) > > > than > > > SPARQL SELECT DISTINCT ?g WHERE { GRAPH ?g { ?s ?p ?o } }; > 37 Rows. -- 522493 msec. > (seem to use only 1 core and CPU up to 100%) > > any idea why not should use the first query in the Conductor "graph" tab > (DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS) to list the graphs ?? > > Thanks, > > Thomas > ------------------------------------------------------------------------------ > _______________________________________________ > Virtuoso-users mailing list > Virtuoso-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/virtuoso-users
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------
_______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
