At MySQL Connect 2013, I talked about how we used MySQL 5.6 at Facebook, and explained some of new features we added to our Facebook MySQL 5.6 source tree. In this post, I'm going to talk about how we made full table scan faster in InnoDB. Faster full table scan in InnoDB In general, almost all queries from applications are using indexes, and reading very few rows (0..1 on primary key lookups and
![Making full table scan 10x faster in InnoDB](https://cdn-ak-scissors.b.st-hatena.com/image/square/e9c13fed6c1afc435a3545a839f2c8b053f6ecdc/height=288;version=1;width=512/https%3A%2F%2Fblogger.googleusercontent.com%2Fimg%2Fb%2FR29vZ2xl%2FAVvXsEg8jOri8mf8FFBQzztvGHOZoE1eP0oqq3XJPM6IOYzzXpp_UU5CHov-nTR_dJh60z_IEYg3zrjwDQLNJeqXbrGz2LypB0FonhGXYfY1Tvfmi8xUpUWNNEux4lrDQ37Jfm52n8l9mn4ww_Q%2Fw1200-h630-p-k-no-nu%2Finnodb_full_table_scan.png)