MySQL Forums
Forum List  »  Optimizer & Parser

Re: Large range query stops using indexes
Posted by: KimSeong Loh
Date: June 12, 2007 09:51PM

Full table scan is more likely to be a "sequential read"

Index scan is always a "random read"

Based on the structure of the hard disk, sequential read is much faster than random read. Even if you have the whole index cached in memory, the reading of the rows out of order can still be slow.

Options: ReplyQuote

Written By
Re: Large range query stops using indexes
June 12, 2007 09:51PM
February 28, 2009 04:49AM

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.