Everybody knows that RDBMS supports indexes.
Everybody knows that indexes can boost SELECT performance.
Many people know that indexes degrades INSERT/UPDATE/DELETE performance.
How do you verify that you are using an index correctly?
How do you estimate how badly INSERT/UPDATE/DELETE are slowed down by indexes?
In this session, I’ll explain detailed mechanism of traditional MySQL B+Tree indexes, optimizer plans and how to boost performance. The following topics will be covered.
Cardinality and Insert ordering are also covered. Suppose you have an product_order table (order_id, order_date, product_id,…) and having indexes on these three columns. order_id is an auto_increment, order_date is inserted by sorted order, product_id is sorted by random order. How these indexes affect performance? How different between storage engines? I’ll show benchmarking results and explain under the hood.
I also cover relationships between Operating system and MySQL index implementation. You should be interested when you realize that Linux i/o scheduler affects index performance.
Yoshinori Matsunobu is a Senior Consultant at MySQL, mainly engaging into consulting services in Japan and Asian countries. He have written five MySQL books, having broad-ranging MySQL technical experties, especially DBA, performance tuning, high availability, i18n and MySQL Cluster.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at email@example.com
Download the MySQL Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the MySQL Conference newsletter.
View a complete list of MySQL contacts.