Re: Partitioning performance issues // 5.1
We're very much looking forward to the improvements talked about in the forum post linked below, and the "Partitioning Under the Hood" talk at the MySQL conference, to prune partitions prior to locking for Insert/Update. We have several large (billion row) MyISAM tables which we highly partitioned, and while this improved some tasks we were disappointed to see no improvement to concurrent inserts due to the locking of all partitions.
"What we will try to do in 5.1 is to improve the lock sort algorithm and in a later version see if we can do the pruning before locking, and that way only lock the needed partitions. (Pruning would also need to support insert, update and delete...)"
http://forums.mysql.com/read.php?106,278885,281256#msg-281256
"In 5.5 a new Meta Data Locking scheme is added which allow us to move the pruning step right after the table meta data lock and before the open/lock calls, so we also can prune open and locking. Allows to prune inserts too. Not yet implemented."
Partitioning Under the Hood in MySQL 5.5
http://en.oreilly.com/mysql2010/public/schedule/detail/13452
Subject
Views
Written By
Posted
4152
February 17, 2010 10:53AM
2468
February 19, 2010 04:17AM
2287
February 19, 2010 10:11AM
2934
February 19, 2010 02:56PM
Re: Partitioning performance issues // 5.1
2603
April 18, 2010 04:51PM
2086
April 18, 2010 11:31PM
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.