When should you anylize a mysql table?

Question

I have a mysql table that has over 10K rows, and is updated with new rows everyday, about 200-300 new rows a day. When I first created the table, I didnt have many index's for the columns and now that I learned its best to index some of the most used queries in the WHERE clause, I'm wondering if it would be a good thing to anylize that table to hopefully speed things up a bit. And if I should, how should I go about doing that?

I have a mysql table that has over 10K rows, and is updated with new rows everyday, about 200-300 new rows a day. When I first created the table, I didnt have many index's for the columns and now that I learned its best to index some of the most used queries in the WHERE clause, I'm wondering if it would be a good thing to anylize that table to hopefully speed things up a bit. And if I should, how should I go about doing that?

I dont use any joins, and the sites not really going slow at all. I was just wondering if it would be good to do it.

Answer 1

A lot of it depends on your where clause itself, and not the indexes. Too many indexes on a table can slow down access anyway. Do you have a date in your query, or a partial string? Are you joining a lot of tables in your query (where you don't have foreign keys set up)? It seems odd that you are getting poor performance with so few rows.

Answer 2

make use of explain statement with select statement
that should show you how the mysql searches for the data you have requested. it also shows you the indexes it is using for searching. By this you can decide which fields you can index.
a tip:something related to
the key buffer ratio should be less 1:1000 which confirms that the performance is good