title: Auto index, repair and optimize MySQL table on every page load
body: <p>I am in a debate with a guy telling me that there is no performance hit for using his function that...</p>
  
  <p>Auto index, repair and optimize MySQL tables using PHP class __destruct() on every single page load by every user who runs the page.</p>
  
  <p>He is asking me why I think it is not good for performance but I do not really know, can someone tell me why such a thing isn't good?</p>
  
  <p><strong>UPDATE</strong> His reasoning...</p>
  
  <p>Optimizing &amp; repairing the database tables eliminates the byte size of overhead that can essentially slow down additional queries when multiple connections and table use are concerned. Even with a performance enhanced database schema with indexing enabled.</p>
  
  <p>Not to mention the amount of execution time to perform these operations are slim to none in memory and processor threading.</p>
  
  <p>Opening, reading, writing, updating and then cleaning up after oneself makes more sense to me then performing the same operations and leaving unnecessary overhead behind waiting for a cron entry to clean up.</p>