Atomicity recovery mechanisms. In cases where you have additional software safeguards, ultra-reliable hardware, or an application that can tolerate a small amount of data loss or inconsistency, you can adjust MySQL settings to trade some of the ACID reliability for greater performance or throughput. The following sections discuss how MySQL features, in particular the  InnoDB  storage engine, interact with the categories of the ACID model: The  atomicity  aspect of the ACID model mainly involves  InnoDB  transactions. Related MySQL features include: The  consistency  aspect of the ACID model mainly involves internal  InnoDB  processing to protect data from crashes. Related MySQL features include: The  isolation  aspect of the ACID model mainly involves  InnoDB  transactions, in particular the isolation level that applies to each transaction. Related MySQL features include: The  durability  aspect of the ACID model involves MySQL software features interacting with your particular hardware configuration. Because of the many possibilities depending on the capabilities of your CPU, network, and storage devices, this aspect is the most complicated to provide concrete guidelines for. (And those guidelines might take the form of “buy new hardware” .) Related MySQL features include: 3003 Durability Isolation Consistency Atomicity • A : atomicity. • C : consistency. • I: : isolation. • D : durability. •The  autocommit  setting. •The  COMMIT  statement. •The  ROLLBACK  statement. •The  InnoDB  doublewrite buffer. See Section 15.6.4, “Doublewrite Buffer” . • InnoDB  crash recovery. See InnoDB Crash Recovery. •The  autocommit  setting. •Transaction isolation levels and the  SET TRANSACTION  statement. See Section 15.7.2.1, “Transaction Isolation Levels” . •The low-level details of  InnoDB  locking. Details can be viewed in the  INFORMATION_SCHEMA  tables (see Section 15.15.2, “InnoDB INFORMATION_SCHEMA Transaction and Locking Information” ) and Performance Schema  data_locks  and  data_lock_waits  tables.