| Question asked
|
In discussing query Q2 (and again for subs … In discussing query Q2 (and again for subsequent queries), it is noted that MonetDB chooses inefficient query execution plans "that mostly use fetch joins, involving merge joins only in a few cases." Based on this, the conclusion goes on to say "relational optimizers may have problems to cope with the specific challenges that arise in the context of RDF." Are we to assume that MonetDB's optimizer performs equally well (or better than) other relational optimizers (including those from industrial implementations such as Oracle and Sybase)? Since the paper purportedly attempts to evaluate storage schemes for RDF, wouldn't a poor optimizer be an orthogonal issue, and a proper evaluation of the storage schemes be based on the best QEP available for each query? on the best QEP available for each query?
|