MySQL Forums
Forum List  »  InnoDB

Re: random-access I/O
Posted by: Aftab Khan
Date: February 08, 2012 11:17PM

>So given that the READs are the slow part of the whole process, the only thing that I can do to speed this up is increase the buffer_pool correct?

Please read James and my replies on your differernt topic 'Mass Import Innodb' which I believe relevent to your query:,512689,514019#msg-514019,512689,514164#msg-514164,512689,514171#msg-514171

>Finally in one of your previous replies you mentioned that partitioning could help me. In my case would it be better to use RANGE or KEY partitioning? With the first option most of the queries will draw data from 1st partition (since the records are sorted by popularity). On the second option the "popular" records will be stored across all partitions. Does MySQL reads multiple partitions at the same time for the same query or is this done in a serial manner?

read this article to understand how mysql decide partition(s) to fecth required records:

Range partitioning - you would have to add a new partition probably each day to keep more "popular" records and from other end you can archive (if required) and delete the oldest partition (the least popular one). However, with KEY partitioning you cannot drop partitions from tables that are partitioned by HASH or KEY in the same way that you can from tables that are partitioned by RANGE or LIST.

If your client(s) would hit the most popular partition then this would improve READs.

Let us know if you require more assistance.

Options: ReplyQuote

Written By
January 31, 2012 03:50AM
January 31, 2012 08:25PM
February 01, 2012 05:19AM
February 03, 2012 01:41AM
February 03, 2012 02:39AM
February 03, 2012 11:08PM
February 04, 2012 08:54AM
February 05, 2012 12:56PM
February 08, 2012 07:22AM
Re: random-access I/O
February 08, 2012 11:17PM
February 09, 2012 05:30AM
February 09, 2012 01:48AM
February 09, 2012 01:58AM
February 09, 2012 10:52AM

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.