1 / 4

2 Old-Fashioned Problems

2 Old-Fashioned Problems. Surajit Chaudhuri Microsoft. Query Optimization Revisited. Great engineering, poorly understood What makes our search algorithm unique? Is our Cardinality Estimation consistent? What are the limits of effective query optimization?

bryanwebb
Télécharger la présentation

2 Old-Fashioned Problems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 2 Old-Fashioned Problems Surajit Chaudhuri Microsoft

  2. Query Optimization Revisited • Great engineering, poorly understood • What makes our search algorithm unique? • Is our Cardinality Estimation consistent? • What are the limits of effective query optimization? • Separate first order and second order assumptions..

  3. Need for Evaluation Frameworks • DB community working on too many “exciting” problems • Hard to know if we are making progress • Isn’t this true of Query Optimizers as well? + Correctness of transformation can be verified • Impact on “real” workload/search efficiency unclear • Automated Physical design + A Technical definition of “optimality”/“goodness” exists - DB2 and Oracle sucks, but I cannot convince you

  4. Need for Evaluation Frameworks (2) • Example : Data Integration (Data Cleaning/Schema Matching) • “Fuzzy” problem specification • No notion of goodness except for “user” validation • Call to Action • Resist temptation to define another new problem with “overlapping” definition • Separate “heuristic”/”knobs” from a concrete server/middleware API • Define evaluation infrastructure (TREC like?) • Otherwise • We will be such like the AI folks..

More Related