Inaccurate MySQL execution plan-Overview

Inaccurate MySQL execution plan-Overview

The execution plan for the Mao MySQL optimizer is often inaccurate, but not optimal (cpu + io )???

Too many factors ::

The information of information_schema is regularly refreshed. In many cases, it is not the most authentic, or even the difference is very large (when it is not a mountain peak, make good use of analyze table and so on );

Now, an enterprise has no money to spend and buys a lot of Solid State disks. It happens that non-intelligent MySQL cannot keep up with the pace of hardware optimization, more than one part of the selection principle may be inaccurate (I believe that other databases are also a pain point );

Environmental factors/

Configuration Factors

And so on...