MySQL Forums
Forum List  »  Optimizer & Parser

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
Re: Optimize - Using Temp, Using Filesort, Group By Having
1789
April 14, 2011 12:08AM


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.