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
4123
November 12, 2014 07:41PM
2176
November 13, 2014 06:40PM
1964
November 14, 2014 03:02AM
1501
November 15, 2014 12:05AM
1568
November 16, 2014 07:39PM
Re: large InnoDB table partitioning without explicit PK
1479
November 17, 2014 04:21PM
1580
November 17, 2014 07:48PM
1569
November 18, 2014 02:00AM
1596
November 18, 2014 11:35PM
1611
November 22, 2014 06:44AM
1482
November 18, 2014 01:13AM
1879
November 19, 2014 12:27AM
1603
November 19, 2014 06:01PM
1750
November 22, 2014 08:39AM
1779
November 14, 2014 03:04AM
1793
November 14, 2014 03:05AM
1830
November 15, 2014 12:32AM
1839
November 16, 2014 08:31PM
1595
November 19, 2014 12:12AM
1529
November 22, 2014 09:07AM
1546
November 23, 2014 09:00PM
1660
December 01, 2014 11:16AM