Looking at a database with 10 tables and fairly active at by-the-hour changes. On the first of each month, I purge some rows from 3 tables to remove outdated material and keep the size down. All of these tables show highlighted (red) 'Overhead' in phpMyAdmin.
Given these conditions, should the tables be OPTIMIZED
just after the purge. If not a good idea, why? (The purge occurs at lowest usage time of day.)
Let's say the tables and current (mid-month) Data & Index sizes are:
Rows Deleted Data Index
table1 17,000 7000 4.3 MiB 1.2 MiB Holds +300/day Transaction Info
table2 6,000 1000 25.5 MiB 231 KiB Holds User Schedule Info
table3 1,800 30 297 KiB 43 KiB Holds User Info
This question is in response to learning about indexes and efforts to reduce slow queries and learning about high counts for:
- Handler read rnd next
- Handler read prev
- Created tmp disk tables
- Opened tables
In reading articles about these items, it seems to be a 'learned' science and requires testing.
Thanks for responding.
Best Answer
Your tables are incredibly small. You should be able to run
very quickly.
Looking at the statistics in your question
If these global status variables present a problem after running
OPTIMIZE TABLE
, this is usually a strong indicator that you have to improve the design of your queries and the size of certain caches.