Hi Pantelis, Do you have “MaxQueryCostEstimationTime” set in the “[SPARQL]” section of the INI file, which is normally commented out by default ? As the "MaxQueryCostEstimationTime” should never be set in the INI file in production use as the Cost Optimizer estimates are generally not accurate and this is more a development/debugging param. Thus the only one that should be set to control query execution time is “MaxQueryExecutionTime".
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 28 Dec 2015, at 12:13, Pantelis Natsiavas <natsia...@gmail.com> wrote: > > Hi everybody. > > I use a Virtuoso instance installed on ubuntu (Virtuoso version: 07.20.3214, > Build: Oct 14 2015), in order to execute sparql queries. My queries are quite > complex and make heavy use of the "OPTIONAL" pattern. While I have used the > same queries on another virtuoso endpoint (not controlled by me) I cannot > seem to use them on mine. I keep getting the message > > "Virtuoso 42000 Error The estimated execution time 0 (sec) exceeds the limit > of 18000 (sec)." > > As you see, I have changed the timeout parameters in the virtuoso.ini file > and put an irrational value (18000 seconds!!!). Still, it seems that the > engine would refuse to execute my query. > > My questions are: > 1. Is the value "0" mentioned as execution time a special value or is it just > a bug? Is it logical to assume that the virtuoso estimates that the query > would require infinite time to execute? > 2. Are there any other configurations that I could do in order to improve > situation? > 3. Is there anything that I should keep in mind when I use the "OPTIONAL" > sparql query pattern? I mean, is there a documented (even informally) way of > improving the performance of queries using OPTIONAL clauses? > > Kind regards, > Pantelis Natsiavas > ------------------------------------------------------------------------------ > _______________________________________________ > 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
