Re: Wrong estimation of Rows in explain
The PARTITIONing provides no performance gain.
The query is asking for 3 million rows from one table, then randomly reaching into the other table 3 million times. Since `innodb_buffer_pool_size` is very small (it should be about 70% of _available_ RAM), the query will have to do a lot of I/O.
I don't see a row estimate of 2; I do see 17. Either of those could be reasonable, since it it not the number of rows in the table, but rather the number of rows in the second table for each row of the first table.
It is usually a mistake to have a pair of columns like this in some table other than a table with "only" these:
AttributeId int(11) ,
AttributeName varchar(100) ,
Do you need 2 billion values for those various IDs? Consider `SMALLINT UNSIGNED` (65K distinct values), or other sizes of INTs. That will save some space.
Subject
Views
Written By
Posted
2147
July 27, 2016 06:19AM
1096
July 27, 2016 08:55AM
1171
July 27, 2016 11:58PM
1036
July 28, 2016 09:14AM
992
July 29, 2016 05:11AM
976
July 29, 2016 01:10PM
Re: Wrong estimation of Rows in explain
1026
July 29, 2016 06:58PM
957
August 02, 2016 05:48AM
1019
August 02, 2016 06:23PM
955
August 02, 2016 05:38AM
974
August 04, 2016 05:31AM
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.