Sandeep Gupta wrote:
Hi,
Our institution is hosting an sparql endpoint which was populated using sponger feature. Due to this we have several named graphs (roughly 30-40). Sometimes we aren't sure which graphs would be relevant for the query so we list all the graphs in a one from clause. Something like this :

Select *
from <graph1>
from <graph2>
from <graph3>
...
....
30 such lines
where
{
 few-simple-predicates


}

//////////////////////////

The predicates aren't too fancy simple relationship chain of size 2-3.

The problem is now is that virtuoso estimates the query time to be 551 secs and doesn't execute the query.
Is there a simple fix for this problem.
Is it possible to query in two stages first finding the graphs where the constants in predicate occurs and then running the original query only those graphs.

P.S. I have tried using bit-map indices but it doesn't help with our query significantly.

Appreciate any help in this regard.

What version of Virtuoso are you running?

Later release do not require you to specify named graphs or build any specific indices.

Also look at you INI file for the current Query Timeout which is affecting your queries. Basically look at the [SPARQL] section [1].


Links:

1. http://docs.openlinksw.com/virtuoso/dbadm.html#ini_SPARQL

Kingsley

Thanks
Sandeep


------------------------------------------------------------------------

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo
------------------------------------------------------------------------

_______________________________________________
Virtuoso-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


--

Regards,

Kingsley Idehen President & CEO OpenLink Software Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen





Reply via email to