Slide 39 has the following name:
Benchmarking partitions - ISOLATION - Try to reproduce working conditions - no other services running while benchmarking - restart the server before each test - Do NOT mix partitioned and unpartitioned tables in the same server - Use MySQL sandbox
Please note that this slide only refers to isolation problems in benchmarking!
This does not apply to starting your server.
If you have table A and table B with identical data and layout, then both should be separated or you will get different results.
This does not apply to the scenario in which you have a large table that shares links to smaller tables, and this is not so, because it makes no sense to split small tables.
Is there any requirement that all tables be partitioned when they are split?
Not
There is absolutely no problem mixing partitioned and regular tables in a database.
In fact, only a few key tables should be partitioned; the rest should not be.
@Mike Purcell: the partition is not designed to protect data, it is designed to speed up access to data, making it easier to exclude unnecessary data from the search.
Consider a log file that breaks into a month.
Usually you are only interested in a narrow time interval of the log file, so the partition will allow MySQL to take into account a much smaller part of the data when viewing the log of a certain period.
Advantages and disadvantages of sections
A partition usually speeds up work by increasing the use of disk space (which in rare cases can slow down).
Sections also make sense only in tables with row lots .
Johan source share