This section describes best practices when using
Using joins wherever data is pulled from multiple tables based on identical ID values from those tables. For fast join performance, define foreign keys on the join columns, and declare those columns with the same data type in each table. Adding foreign keys ensures that referenced columns are indexed, which can improve performance. Foreign keys also propagate deletes or updates to all affected tables, and prevent insertion of data in a child table if the corresponding IDs are not present in the parent table.
Turning off autocommit. Committing hundreds of times a second puts a cap on performance (limited by the write speed of your storage device).
Grouping sets of related DML operations into transactions, by bracketing them with
COMMITstatements. While you don't want to commit too often, you also don't want to issue huge batches of
DELETEstatements that run for hours without committing.
InnoDBcan handle multiple sessions all reading and writing to the same table at once, without sacrificing reliability or high performance. To get exclusive write access to a set of rows, use the
SELECT ... FOR UPDATEsyntax to lock just the rows you intend to update.
innodb_file_per_tableoption to put the data and indexes for individual tables into separate files, instead of the system tablespace. This setting is required to use some of the other features, such as table compression.
Evaluating whether your data and access patterns benefit from the
InnoDBtable compression feature. You can compress
InnoDBtables without sacrificing read/write capability.
Running your server with the option
--sql_mode=NO_ENGINE_SUBSTITUTIONto prevent tables being created with a different storage engine if there is an issue with the engine specified in the