MySQL Forums
Forum List  »  Performance

Re: Very slow SELECT on 13.000 Rows
Posted by: Rick James
Date: December 29, 2010 04:33PM

InnoDB 'clusters' the PRIMARY KEY with the data. You have no secondary keys. So, I would expect Index_length to be essentially 0. Please do SHOW TABLE STATUS.

To assist in analyzing slow SELECTs, please provide
* SHOW CREATE TABLE tbl\G -- engine, indexes
* SHOW TABLE STATUS LIKE 'tbl'\G -- sizes
* EXPLAIN SELECT ...\G -- clues of inefficiencies
* SHOW VARIABLES LIKE '%buffer%'; -- cache size
and surround them with [ code ] and [ / code ]
Please do those on both setups -- something may be different between them.
How much RAM?

Your PRIMARY KEY is BINARY(16). Does this mean it is a GUID or UUID or MD5? Such keys are _very_ random. Once the data becomes bigger than cache, the processing becomes I/O-bound.

I see no indexes to support the JOINs.

(This board is fine for the question. Please provide the above info, and we can dig deeper.)

Options: ReplyQuote


Subject
Views
Written By
Posted
2762
December 28, 2010 02:08PM
Re: Very slow SELECT on 13.000 Rows
944
December 29, 2010 04:33PM
2001
January 01, 2011 12:01PM
969
January 02, 2011 02:45AM
1041
January 02, 2011 04:13AM
894
January 02, 2011 10:44AM
885
January 11, 2011 02:11PM


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.