Re: Optimize - Using Temp, Using Filesort, Group By Having
Posted by:
Rick James
Date: April 14, 2011 12:08AM
KEY `complete` (`complete`), -- this is now redundant (because of (complete, due_time)); recommend DROPing the shorter one.
tracking_number 767 -- that's a bulky index. Every secondary index (in InnoDB) contains a copy of the PK. That's 6 (or 5) copies of it. Is it really VARCHAR(255)? Is it really utf8? Could you use a surrogate AUTO_INCREMENT instead?
innodb_buffer_pool_size 112197632 -- probably too small; see
http://mysql.rjweb.org/doc.php/memory
VARCHAR(255) and TINYTEXT are very similar; VARCHAR(255) has an advantage in certain temp table situations.
Subject
Views
Written By
Posted
5669
April 08, 2011 10:40AM
2120
April 09, 2011 11:37PM
1641
April 12, 2011 01:38PM
2292
April 13, 2011 07:56AM
1640
April 13, 2011 09:44AM
Re: Optimize - Using Temp, Using Filesort, Group By Having
2184
April 14, 2011 12:08AM
2221
April 19, 2011 12:18PM
1630
April 19, 2011 10:40PM
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.