Re: [Virtuoso-users] Bad query performance when selecting from two graphs

2009-11-23 Thread Mirko
Hi Ivan, hi Hugh, ok, I wasn't aware of the need for additional indices for multiple graph RDF queries. I solved my issue by creating two bitmap indices (P,O,G,S) and (P,S,O,G). Thanks for your help, Mirko Am 22.11.2009 um 06:34 schrieb Ivan Mikhailov: > Hello Mirko, > > What indexes do you

Re: [Virtuoso-users] Bad query performance when selecting from two graphs

2009-11-22 Thread Ivan Mikhailov
Hello Mirko, What indexes do you have? You may need at least bitmap SPOG index for the first query. The default layout (only two indexes) works for queries taht have all graphs fixed (or calculated before use), but not for all other queries. Best Regards, Ivan Mikhailov OpenLink Software http://

Re: [Virtuoso-users] Bad query performance when selecting from two graphs

2009-11-21 Thread Hugh Williams
Hi Mirko, Running similar queries with ORDER BY and LiMIT query modifier against my Virtuoso 5.0.12 build and do not observe the behaviour you report. What Virtuoso release are you testing against ? Also, can you provide the output of running the explain () function which describes the query

[Virtuoso-users] Bad query performance when selecting from two graphs

2009-11-20 Thread Mirko
Hi, I have a SPARQL query which performes well when querying a single graph but "the estimated execution time exceeds the time limit of 400 (secs)" when querying two graphs. This is also true if the second graph is empty. Why is this the case / how can I fix this? Query A (performes well): SEL