Skip navigation links

MySQL Forums :: Optimizer & Parser :: Optimize - Using Temp, Using Filesort, Group By Having


Advanced Search

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.

Options: ReplyQuote


Subject Views Written By Posted
Optimize - Using Temp, Using Filesort, Group By Having 3495 Lenny Dunn 04/08/2011 10:40AM
Re: Optimize - Using Temp, Using Filesort, Group By Having 1165 Rick James 04/09/2011 11:37PM
Re: Optimize - Using Temp, Using Filesort, Group By Having 896 Lenny Dunn 04/12/2011 01:38PM
Re: Optimize - Using Temp, Using Filesort, Group By Having 1475 Rick James 04/13/2011 07:56AM
Re: Optimize - Using Temp, Using Filesort, Group By Having 853 Lenny Dunn 04/13/2011 09:44AM
Re: Optimize - Using Temp, Using Filesort, Group By Having 1482 Rick James 04/14/2011 12:08AM
Re: Optimize - Using Temp, Using Filesort, Group By Having 1343 Lenny Dunn 04/19/2011 12:18PM
Re: Optimize - Using Temp, Using Filesort, Group By Having 789 Rick James 04/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.