InnoDB assumes it's using conventional disks, where random I/O is much more expensive than sequential I/O because of
the time it take to seek to the correct location on disk and wait for the desired part of the disk to rotate under the head.

MySQL: The innoDB transaction log

InnoDB uses its log to convert the random disk I/O to sequential I/O.

Of course, InnoDB does ultmately have to write the changes into  data files, because the log file size is fixed.

InnoDB uses a background thread to flush the changes to the data files intelligiently.

The overall log file size is controlled by the innodb_log_file_size and innodb_log_files_in_group , and it's very important for
 write performance.

InnoDB uses multiple files as a single circular log.

 

相关文章:

  • 2021-09-15
  • 2021-09-20
  • 2021-04-30
  • 2021-09-07
  • 2022-12-23
  • 2021-09-24
  • 2022-12-23
  • 2021-12-18
猜你喜欢
  • 2021-08-06
  • 2022-12-23
  • 2021-06-18
  • 2021-08-27
  • 2021-12-13
  • 2022-12-23
  • 2021-07-16
相关资源
相似解决方案