Re: Rows Examined, why so many?
http://hackmysql.com/joinrows is my understanding of this. That is, it has to do with how MySQL joins tables, which causes the number of rows examined (i.e., read), to be different from the actual number of rows produced (i.e., returned). If you have a dead quiet test server, or are using MySQL 5.0.2 or higher, I suggest:
1. FLUSH STATUS;
2. Run the query
3. SHOW STATUS LIKE 'Handler_read%';
The Handler_read_* values give good insight into what kind of activity MySQL runs itself through while doing a join. Sometimes, through these values you can trace exactly what MySQL does (knowing first how it joins tables, and then not always because it has optimizations which allow it to work less).
Subject
Views
Written By
Posted
21309
September 20, 2005 12:15PM
Re: Rows Examined, why so many?
9551
September 20, 2005 03:18PM
5913
September 21, 2005 08:12AM
4780
September 20, 2005 03:54PM
4346
September 20, 2005 07:10PM
4173
September 21, 2005 05:05AM
4086
September 21, 2005 08:13AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.