Hi Thomas, Yes, "AdjustVectorSize = 0” as it is the new default in 7.2.2 both in the INI files and if not set, following similar problems display/counting of graphs and queries with long execution times …
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 12:03, Thomas Michaux <mich...@abes.fr> wrote: > > yes it's improving (i added some grpah meanwhile so 46 rows is the correct > number) : > > SPARQL SELECT DISTINCT ?g WHERE { GRAPH ?g { ?s ?p ?o } }; > 46 Rows. -- 1337 msec. > > DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS(); > 46 Rows. -- 434 msec. > > I had already VectorSize = 1000 in virtuoso.ini but I had > AdjustVectorSize = 1 so changing to 0 has an effect > > We have 232 973 825, read only use case mainly, is it ok to keep > AdjustVectorSize = 0 has documentation says it will be better to > improve performance with = 1 ? > > Thanks, > > Thomas > > > Le 05/04/2016 12:52, Hugh Williams a écrit : >> 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
