MySQL Forums
Forum List  »  Partitioning

Re: Impact of larger partition number on database performance
Posted by: Mikael Ronström
Date: May 31, 2007 01:15AM

A high number of partitions will increase the load to some extent
given that there are more files to scan. Normally it should be
quite ok to have at least 10-20 million records per partition
at least and sometimes even more. So you can probably decrease the
number of partitions significantly.

The major cost when having large numbers of partitions is the cost
to open the table which essentially means that 1000 partitions have
to be opened. Opening of a table happens when the current table
is used by another connection or when the table is not present in
the cache.

Rgrds Mikael

Kamal Joshi Wrote:
> Hi,
> We have done partitioning of a big table:
> Records = 57 millions
> Number of Partitions = 1000
> Partition type = hash
> After the partition, we are facing high CUP usage
> problem even for the low load in database.
> Is this because of the partitioning with large
> number (1000) of partitions?
> If yes, then what should be the ideal number of
> partitions in this case for better performance?
> Please help!
> Thanks,
> Kamal Joshi

Options: ReplyQuote

Written By
Re: Impact of larger partition number on database performance
May 31, 2007 01:15AM

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.