InnoDB Read-Only Transactions_只读事务

InnoDB读取优化：减少不必要的事务ID，提升报表生成应用性能

最新推荐文章于 2024-12-12 18:59:36 发布

转载最新推荐文章于 2024-12-12 18:59:36 发布 · 279 阅读

0 ·

CC 4.0 BY-SA版权

原文链接：https://my.oschina.net/xinxingegeya/blog/342767

文章标签：

#数据库 #python

文章介绍如何利用InnoDB的读取优化特性，通过减少不必要的事务ID来降低内部数据结构的查询开销，从而提高报表生成应用的性能。重点在于将一系列InnoDB查询组织在STARTTRANSACTIONREADONLY和COMMIT中，或在开启自动提交模式下运行，以避免锁定操作，实现高效的读取操作。

2019独角兽企业重金招聘Python工程师标准>>>

InnoDB Read-Only Transactions_只读事务

官方文档：http://dev.mysql.com/doc/refman/5.6/en/innodb-performance-ro-txn.html

‍As of（自从） MySQL 5.6.4, InnoDB can avoid the overhead associated with setting up the transaction ID (TRX_ID field) for transactions that are known to be read-only. A transaction ID is only needed for a transaction that might perform write operations or locking reads such as SELECT ... FOR UPDATE. Eliminating（排除） unnecessary transaction IDs（不必要的transaction id） reduces（降低） the size of internal data structures that are consulted（商量，顾及） each time a query or DML（数据操纵语言） statement constructs a read view.

Currently, InnoDB detects（发现，发觉） read-only transactions when:

The transaction is started with the START TRANSACTION READ ONLY statement. In this case, attempting to make changes to the database (for InnoDB, MyISAM, or other types of tables) causes an error, and the transaction continues in read-only state:
ERROR 1792 (25006): Cannot execute statement in a READ ONLY transaction.
You can still make changes to session-specific temporary（临时的） tables in a read-only transaction, or issue locking queries for them, because those changes and locks are not visible to any other transaction.
The autocommit setting is turned on（打开）, so that the transaction is guaranteed to be a single statement, and the single statement making up the transaction is a “non-locking” SELECT statement. That is, a SELECT that does not use a FOR UPDATE or LOCK IN SHARED MODE clause.

InnoDB默认的read only有两种方式：

The transaction is started with the START TRANSACTION READ ONLY statement.
The autocommit setting is turned on（打开）.

Thus, for a read-intensive（加强的，强烈的） application such as a report generator, you can tune （调整使协调）a sequence of InnoDB queries by grouping them inside START TRANSACTION READ ONLY and COMMIT, or by turning on the autocommit setting before running the SELECT statements, or simply by avoiding any DML statements interspersed（散开的） with the queries.

==================END==================

转载于:https://my.oschina.net/xinxingegeya/blog/342767