Quote: InnoDB must flush the log to disk at each transaction commit, if that transaction made modifications to the database. Since the rotation speed of a disk is typically at most 167 revolutions/second, that constrains the number of commits to the same 167/second if the disk does not fool the operating system.
It looks like InnoDB only needs one cache flush per transaction, while Sqlite needs two. Why is this the case? What does sqlite do differently? Can the pager layer be modified to handle this differently? /Ludvig
