Re: large InnoDB table partitioning without explicit PK
Posted by:
Rick James
Date: November 17, 2014 04:21PM
> * from Table1 where col2 like '2014-11-16 1%';
-->
WHERE col1 >= '2014-11-16 10:00:00'
AND col1 < '2014-11-16 10:00:00' + INTERVAL 10 HOUR
> [Miko] You mean analyse/check/optimise/repair table, is it correct?
No. Things like walking through the table to delete parts of it, or to study the values. As I say, subtle.
> [Miko] There will be a "fresh" installation with empty DB from the very beginning.
> But I still need to test performance degradation. This is my biggest headache I have to say.
Because of the eventual size of the table (and other issues), your testing should get a lot closer to the eventual size. We are seeing some issues now, but there may be bigger issues as it grows. The insertion rate going from 5M -> 50M scares me the most. (Hence, I have dwelled on it.) Having all the activity in a single partition that is 1% of the total makes it all feasible.
The concern over the binlog may be solved via RBR.
Subject
Views
Written By
Posted
4509
November 12, 2014 07:41PM
2300
November 13, 2014 06:40PM
2071
November 14, 2014 03:02AM
1604
November 15, 2014 12:05AM
1645
November 16, 2014 07:39PM
Re: large InnoDB table partitioning without explicit PK
1583
November 17, 2014 04:21PM
1680
November 17, 2014 07:48PM
1649
November 18, 2014 02:00AM
1713
November 18, 2014 11:35PM
1703
November 22, 2014 06:44AM
1571
November 18, 2014 01:13AM
2008
November 19, 2014 12:27AM
1721
November 19, 2014 06:01PM
1940
November 22, 2014 08:39AM
1874
November 14, 2014 03:04AM
1908
November 14, 2014 03:05AM
1921
November 15, 2014 12:32AM
1935
November 16, 2014 08:31PM
1721
November 19, 2014 12:12AM
1633
November 22, 2014 09:07AM
1644
November 23, 2014 09:00PM
1815
December 01, 2014 11:16AM