Table summary

Decision to optimize particular tables for many is driven by the condition of the table. Personally, I use "Site Documentation" module to figure out which tables need most attention and then rely on this module to automate the process.

I bet many have not discovered this winning combination. So adding a table summary a la sitedoc, and maybe even the statistics (do I hear "a chart"?) of the past optimizations will kick ass!