Performance Tuning Best Practices for MySQL
Why Stack Overflow recommends it
Stack Overflow users link it when answering MySQL performance and query-optimization questions, pointing to it as a practical overview of tuning and indexing practices.
Recommended by 3 people across 3 different months, 2008 to 2017.
What it is
A 2006 Google Tech Talk in which Jay Pipes, co-author of Pro MySQL, explains where to focus when tuning MySQL servers and applications. It covers finding the low-hanging fruit among bottlenecks, with topics like indexing, schema choices and avoiding correlated subqueries.
What people said
Recommends VP. · 2008-09 · Stack Overflow · on “MySQL Training videos”
In youtube you find somethings like mysql install: [LINK] mysql trainning: [LINK] Google presentation about mysql tunning (hot) [this video] You have anothers google presentations about mysql, just search in youtube and googlevideos :-)
Recommends DBMarcos99 · 2009-07 · Stack Overflow · on “How do I ask for help optimizing & fixing queries in MySQL?”
Knowing which indexes you have on the tables concerned is vital, imo. You state you are using a substring of column_bar in the where clause - you may need to denormalize and store this substring in another column and then index it. There again cardinality of the column can make it worthless using an index on that column, if (for example) there are only 2 distinct values present. For a useful video tutorial on Performance Tuning Best Practices watch this [this video] by Jay Pipes.
Recommends Yada · 2009-12 · Stack Overflow · on “MySql and inline SELECTs”
Try to avoid correlated subqueries by using JOIN if you can. Watch this great video on MySQL performance on [this video] . Go to 31:00 minute in. The speaker Jay Pipes talks about avoiding correlated subqueries.
Cites Sam · 2017-08 · Stack Overflow · on “Django MySQL database design”
Thanks, I'll try adding `db_index=True`. Here [this video] is where I got the recommendation to split the table. Since it's a Google Tech Talk, I have no reason to doubt it was relevant when it came out, but, obviously 2007 was a long time ago, so maybe the technology has changed since then?