transactions cease to operate and their business grind to a halt. 6. Optimization Guidelines BKM innodb_thread_concurrency. Different values were tried; the best performance came with the default 0 (unlimited MySQL with SSDs Page 8 BKM innodb_adaptive_hash_index. Turned ‘OFF’, since OLTP workloads typically do not reuse data from previous queries. BKM innodb_fill_factor. Indicates the percentage mestamp innodb_log_group_home_dir //mysql_log Best Practices for MySQL with SSDs Page 13 innodb_undo_directory //mysql_log innodb_buffer_pool_size

55 Present - Solutions! 2016 - M ySQL InnoDB Cluster MySQL 组复制:自动成员身份更改、网络分区处理、一致性... MySQL Shell 提供强大的界面，有助于自动化和集成所有组件 InnoDB 克隆以自动生成成员，完全集成在InnoDB 中 MySQL Router MySQL Server RPO =0 RTO 自动故障转移) Copyright @ 2021 Oracle and/or its affiliates. 9 / 55 Present - Solutions! 2020 - MySQL InnoDB Replicaset • "经典"、"异步"的基于复制的解决方案，完全集成 • MySQL Shell • MySQL Router • MySQL Server RPO Oracle and/or its affiliates. MySQL InnoDB ClusterSet Copyright @ 2021 Oracle and/or its affiliates. 13 / 55 一个或者多个MySQL InnoDB Cluster 副本连接到一个主MySQL InnoDB Cluster 高可用 (区域内的失败) RPO =0 RTO

优化方式 优化方式  MySQL MySQL 技巧分享 技巧分享  Q Q & & AA MyISAM MyISAM 特点 特点 MyISAM vs MyISAM vs InnoDB InnoDB • 数据存储方式简单，使用 数据存储方式简单，使用 B+ Tree B+ Tree 进行索引 进行索引 • 使用三个文件定义一个表： 使用三个文件定义一个表： .MYI 不支持一些数据库特性，比如 事务、外键约束等 • Table level lock Table level lock ，性能稍差，更适合读取多的操作 ，性能稍差，更适合读取多的操作 InnoDB InnoDB 特点 特点 •使用 使用 Table Space Table Space 的方式来进行数据存储 的方式来进行数据存储 (ibdata1, ib_logfile0) (ibdata1 MySQL 服务器，尽量在应用本身达到一 服务器，尽量在应用本身达到一 个 个 MySQL MySQL 最合理的使用 最合理的使用  针对 针对 MyISAM MyISAM 或 或 InnoDB InnoDB 不同引擎进行不同定制 不同引擎进行不同定制 性配置 性配置  针对不同的应用情况进行合理配置 针对不同的应用情况进行合理配置  针对 针对 my.cnf my.cnf 进行配置，后面设置是针对内存为

displaying BLOB-data as image or download-link track changes on databases, tables and views support InnoDB tables and foreign keys support mysqli, the improved MySQL extension see 1.17 Which Database versions $cfg['BrowseMIME'] boolean true Enable Transformations. $cfg['MaxExactCount'] integer 500000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT will be used, otherwise the approximate count will be used. See also 3.11 The number of rows for InnoDB tables is not correct. $cfg['MaxExactCountViews'] integer 0 For VIEWs, since obtaining the exact

displaying BLOB-data as image or download-link track changes on databases, tables and views support InnoDB tables and foreign keys support mysqli, the improved MySQL extension see 1.17 Which Database versions $cfg['BrowseMIME'] boolean true Enable Transformations. $cfg['MaxExactCount'] integer 50000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT in version 4.2.6: The default value was changed to 500000. See also 3.11 The number of rows for InnoDB tables is not correct. $cfg['MaxExactCountViews'] integer 0 For VIEWs, since obtaining the exact

displaying BLOB-data as image or download-link track changes on databases, tables and views support InnoDB tables and foreign keys support mysqli, the improved MySQL extension see 1.17 Which Database versions $cfg['BrowseMIME'] boolean true Enable Transformations. $cfg['MaxExactCount'] integer 50000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT in version 4.2.6: The default value was changed to 500000. See also 3.11 The number of rows for InnoDB tables is not correct. $cfg['MaxExactCountViews'] integer 0 For VIEWs, since obtaining the exact

displaying BLOB-data as image or download-link track changes on databases, tables and views support InnoDB tables and foreign keys support mysqli, the improved MySQL extension see 1.17 Which Database versions $cfg['BrowseMIME'] boolean true Enable Transformations. $cfg['MaxExactCount'] integer 50000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT in version 4.2.6: The default value was changed to 500000. See also 3.11 The number of rows for InnoDB tables is not correct. $cfg['MaxExactCountViews'] integer 0 For VIEWs, since obtaining the exact

displaying BLOB-data as image or download-link track changes on databases, tables and views support InnoDB tables and foreign keys support mysqli, the improved MySQL extension see 1.17 Which Database versions $cfg['BrowseMIME'] boolean true Enable Transformations. $cfg['MaxExactCount'] integer 50000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT in version 4.2.6: The default value was changed to 500000. See also 3.11 The number of rows for InnoDB tables is not correct. $cfg['MaxExactCountViews'] integer 0 For VIEWs, since obtaining the exact

displaying BLOB-data as image or download-link track changes on databases, tables and views support InnoDB tables and foreign keys support mysqli, the improved MySQL extension see 1.17 Which Database versions $cfg['BrowseMIME'] boolean true Enable Transformations. $cfg['MaxExactCount'] integer 50000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT value: Type: Default value: Type: Default value: Type: Default value: 3.11 The number of rows for InnoDB tables is not correct. $cfg['MaxExactCountViews'] integer 0 For VIEWs, since obtaining the exact

displaying BLOB-data as image or download-link track changes on databases, tables and views support InnoDB tables and foreign keys support mysqli, the improved MySQL extension see 1.17 Which Database versions $cfg['BrowseMIME'] boolean true Enable Transformations. $cfg['MaxExactCount'] integer 50000 For InnoDB tables, determines for how large tables phpMyAdmin should get the exact row count using SELECT COUNT in version 4.2.6: The default value was changed to 500000. See also 3.11 The number of rows for InnoDB tables is not correct. $cfg['MaxExactCountViews'] integer 0 For VIEWs, since obtaining the exact