We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

MariaDB and MySQL — what statistics optimizer needs

Formal Metadata

Title
MariaDB and MySQL — what statistics optimizer needs
Subtitle
or when and how not to use indexes
Title of Series
Number of Parts
94
Author
License
CC Attribution 4.0 International:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
In this talk you'll learn what data statistics MariaDB and MySQL can collect, what statements do that, how to tell the optimizer to use it (it won't necessarily do it automatically!) and how it can make your queries many times faster. When your SQL query reaches the DBMS, it's the optimizer's job to decide how to execute it for you to get the result as fast as possible. To make this decision optimizer can examine the actual table data, but with multi gigabyte and terabyte tables, the only practical solution is to use various data statistics that were collected in advance. The better the statistics and the more precisely it describes the actual data, the faster the plan will be, because the optimizer image of reality will be closer to the actual reality. In this talk you'll learn what data statistics MariaDB and MySQL can collect, what statements do that, how to tell the optimizer to use it (it won't necessarily do it automatically!) and how it can make your queries many times faster. And, of course, when not to use indexes, when up-to-date statistics is enough.