Voila, Indexes! A Look at Some Simple Preventative Magick
summary
A concrete claim: shipping tables without indexes causes full table scans that explode as data grows — the example generates one scroll per minute reaching 700 scrolls by sunset and thousands in days — and the remedy is to add targeted indexes (foreign keys, multi-column for sorted queries) at creation time. Tooling shown: Rails migrations, MySQL EXPLAIN to see plans (look for the dreaded ALL), and measurements prove selective indexing cuts work and latency dramatically.
AI-written summary · about
chapters (11)
- 0:00Basil and Fabian intro
- 3:47Library without indexes
- 7:58Indexing everything leads to disaster
- 12:34Why indexes hurt performance
- 14:57Foreign keys as index start
- 17:26Multi-column indexes uses
- 20:37When multi-column indexes help
- 23:03Sort columns indexing
- 24:26EXPLAIN index usage
- 29:23Optimizing with EXPLAIN
- 31:31Database index best practices
related talks
46mSupercharge Your SQL with Indexes: a Practical Introduction
49mIt’s Not Always About the Index: The Hidden Secrets of Query Performance
42mThings every developer absolutely, positively needs to know about database indexing
36mFor performance, go to page 5: Indexes
01mHow well do you know your MySQL Indexes?
01h 00m7 Tips to Performance Tuning, Optimization, and Everything
50mHow to choose the right index
25mThe Secret Life of SQL: How to Optimize Database Performance