Bug #71971 | Update disk optimization advice | ||
---|---|---|---|
Submitted: | 7 Mar 2014 12:05 | Modified: | 17 Mar 2017 18:29 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.6 | OS: | Any |
Assigned to: | Daniel Price | CPU Architecture: | Any |
[7 Mar 2014 12:05]
Daniël van Eeden
[7 Mar 2014 12:25]
MySQL Verification Team
Thank you for the bug report.
[28 May 2015 19:04]
Daniel Price
Posted by developer: The referenced documentation was updated to include mention of storing InnoDB tables outside of the MySQL data directory (i.e. using the DATA DIRECTORY option when creating file-per-table tablespaces. In 5.7, general tablespaces can also be created outside of the MySQL data directory.
[17 Mar 2017 18:29]
Daniel Price
Posted by developer: Revisions were made to the following sections: https://dev.mysql.com/doc/refman/5.7/en/disk-issues.html https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-diskio.html Requested information was added to "Optimizing InnoDB Disk I/O" https://dev.mysql.com/doc/refman/5.7/en/optimizing-innodb-diskio.html Changes should appear online within 24 hours. Thank you for the bug report.