Re: Range Access for Multiple-Part Indexes
Posted by:
Rick James
Date: January 01, 2010 09:23PM
Do you have the Query cache turned on? How well is it being used (SHOW GLOBAL STATUS LIKE 'qc%')?
8 cores is sometimes worse than 4. Are things other than MySQL running on this box?
What order is the data inserted into the table? (I am fishing for whether the _data_ can be ordered in a more optimal way.)
Speaking of ordering the data, InnoDB keeps the data in PRIMARY KEY order. Switching to that engine _may_ help. In doing so, carefully pick the PK, watch out for the data being larger, and the cache VARIABLES need changing. Experiment with one table first.
Is there any pattern of which of x, y, year has the biggest range? That is, if (say) most of the 'year's are requested, then it may be better for year to be the last part of the index (as it is).
Care to tell me what the data represents?
Subject
Views
Written By
Posted
4307
December 30, 2009 03:52PM
2312
December 31, 2009 08:11PM
2517
January 01, 2010 03:52PM
2396
January 01, 2010 04:37PM
2198
January 01, 2010 05:23PM
Re: Range Access for Multiple-Part Indexes
2197
January 01, 2010 09:23PM
2468
January 02, 2010 12:54AM
2262
January 02, 2010 09:41PM
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.