MySQL Forums
Forum List  »  Optimizer & Parser

Re: best way to optimize this query
Posted by: Rick James
Date: July 15, 2012 10:11PM

INDEXes are (often) useful for finding a few rows out of many. You need to look at all the rows, so an index is more trouble than it is worth. Hence, the "table scan".

Solution? Often it is building and incrementally maintaining a "summary table". You have not divulged much info, so I can't be very specific.

Here are some examples:

summary -,421092 (Large Table Architecture)
partition, summary -,288561 (Partitioning with range(to_days) issue)
data warehouse, summary -,252723 (Database Design for huge set of data)
summary -,252593 (Counters)
locks, summary tables -,247124 (Solving table locking issues)
summary -,245133 (Design approach for summary table by 3 items)
summary table -,428050 (To store or calculate on the spot?)
ummary -,393184 (Storing a large, dense tensor (35gb scientific data) -- is mysql appropriate?)
summary -,364300 (Thinking about sorting articles..)
summary -,359476 (Slow 'sending data' phase on mySQL query, for simple query)
summary -,298557 (UNIX_TIMESTAMP Duplicate key)
ALTER, summary -,287739 (Large table designissue)
huge, summary tables -,282768 (Which storage engine?)
summary -,266570 (Best way to store/access large amounts of data?)
summary, using index -,253221 (InnoDB CPU Spikes)
summary -,254332 (Very long query doubt... (Monster query...))
summary -,247779 (compressing tables)
summary -,372008 (Index performance)
summary -,294180 (Multiple complex queries)
left_off, myisam vs innodb, summary -,276359 (should i go with myisam or innodb?)

Options: ReplyQuote

Written By
July 14, 2012 09:54AM
Re: best way to optimize this query
July 15, 2012 10: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.