content_image/735699.jpg content_image/735700.jpg
innodb_fil_make_page_dirty_debug  option is only available if debugging support is compiled in using the WITH_DEBUG CMake  option. 

• innodb_file_per_table 

<img src='content_image/735699.jpg'>

When innodb_file_per_table  is enabled, tables are created in file-per-table tablespaces by default. When disabled, tables are created in the system tablespace by default. For information about file- per-table tablespaces, see Section 15.6.3.2, “File-Per-Table Tablespaces” . For information about the InnoDB  system tablespace, see Section 15.6.3.1, “The System Tablespace” . 

The innodb_file_per_table  variable can be configured at runtime using a SET GLOBAL  statement, specified on the command line at startup, or specified in an option file. Configuration at runtime requires privileges sufficient to set global system variables (see Section 5.1.9.1, “System Variable Privileges” ) and immediately affects the operation of all connections. 

When a table that resides in a file-per-table tablespace is truncated or dropped, the freed space is returned to the operating system. Truncating or dropping a table that resides in the system tablespace only frees space in the system tablespace. Freed space in the system tablespace can be used again for InnoDB  data but is not returned to the operating system, as system tablespace data files never shrink. 

The innodb_file_per-table  setting does not affect the creation of temporary tables. As of MySQL 8.0.14, temporary tables are created in session temporary tablespaces, and in the global temporary tablespace before that. See Section 15.6.3.5, “Temporary Tablespaces” . 

• innodb_fill_factor 

<img src='content_image/735700.jpg'>

InnoDB  performs a bulk load when creating or rebuilding indexes. This method of index creation is known as a “sorted index build” . 

innodb_fill_factor  defines the percentage of space on each B-tree page that is filled during a sorted index build, with the remaining space reserved for future index growth. For example, setting innodb_fill_factor  to 80 reserves 20 percent of the space on each B-tree page for future index 

