Quantcast

[jira] [Created] (DERBY-6921) How good is the Derby Query Optimizer, really

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Created] (DERBY-6921) How good is the Derby Query Optimizer, really

JIRA jira@apache.org
Bryan Pendleton created DERBY-6921:
--------------------------------------

             Summary: How good is the Derby Query Optimizer, really
                 Key: DERBY-6921
                 URL: https://issues.apache.org/jira/browse/DERBY-6921
             Project: Derby
          Issue Type: Improvement
          Components: SQL
            Reporter: Bryan Pendleton
            Priority: Minor


At the 2015 VLDB conference, a team led by Dr. Viktor Leis at Munich
Technical University introduced a new benchmark suite for evaluating
database query optimizers: http://www.vldb.org/pvldb/vol9/p204-leis.pdf

The benchmark test suite is publically available:
http://db.in.tum.de/people/sites/leis/qo/job.tgz

The data set for running the benchmark is publically available:
ftp://ftp.fu-berlin.de/pub/misc/movies/database/

As part of Google Summer of Code 2017, I am volunteering to mentor
a Summer of Code intern who is interested in using these tools to
improve the Derby query optimizer.

My suggestion for the overall process is this:
1) Acquire the benchmark tools, and the data set
2) Run the benchmark.
2a) Some of the benchmark queries may reveal bugs in Derby.
     For each such bug, we need to isolate the bug and fix it.
3) Once we are able to run the entire benchmark, we need to
   analyze the results.
3a) Some of the benchmark queries may reveal opportunities
   for Derby to improve the query plans that it chooses for
   various classes of queries (this is explained in detail in the
   VLDB paper and other information available at Dr. Leis's site)
   For each such improvement, we need to isolate the issue,
   report it as a separable improvement, and fix it (if we can)

While the benchmark is an interesting exercise in and of itself,
the overall goal of the project is to find-and-fix problems in the
Derby query optimizer, specifically in the 3 areas which are
the focus of the benchmark tool:
1) How good is the Derby cardinality estimator and when does
   it lead to slow queries?
2) How good it the Derby cost model, and how well is it guiding
   the overall query optimization process?
3) How large is the Derby enumerated plan space, and is it
   appropriately-sized?

While other Derby issues have been filed against these questions
in the past, the intent of this specific project is to use the concrete
tools provided by the VLDB paper to make this effort rigorous and
successful at making concrete improvements to the Derby query
optimizer.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
Loading...