 | ||
| How the atomic write I/O feature of Storage Foundation helps MySQL databases | ||
|---|---|---|
| Prev | Improving database performance with atomic write I/O | Next |
| ||
| How the atomic write I/O feature of Storage Foundation helps MySQL databases | ||
|---|---|---|
| Prev | Improving database performance with atomic write I/O | Next |
Database applications are required to maintain Atomicity, Consistency, Isolation, Durability (ACID) properties for data integrity. The InnoDB storage engine of MySQL writes twice to achieve atomicity: once to the double write buffer and once to the actual tablespace. With an atomic write I/O, the writes to the double write buffer can be avoided, resulting in better performance and longer lifetime of the SSD.
Storage Foundation supports atomic write I/O in the following situations:
directly on raw VxVM volumes
on VxFS file systems on top of VxVM volumes
This scenario supports the MySQL capability of auto-extending the configured databases dynamically. If the database files consume all of the space on the file system, then you can grow the underlying file system and volume dynamically.
See Dynamically growing the atomic write capable file system.