[MDEV-11396] AliSQL: [perf] Issue#12 OPTIMIZE INNODB READ-ONLY WORKLOAD Created: 2016-11-29  Updated: 2016-11-30  Resolved: 2016-11-30

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Lixun Peng
Resolution: Won't Do Votes: 0
Labels: None

Epic Link: AliSQL patches

 Description   

Description:
------------
These path introduces several improvement for InnoDB read-only
workload:
 
1. Remove trx_sys_t::ro_trx_list, all transaction will start with
read only mode, and change to rw mode while encountering DML
statement. For more details, refer to mysql worklog WL#6047.
 
2. Read view object is cached for read-only statement if no rw
statement happens during two read only statements of the same
session.
 
3. Ignore acquiring lock_sys mutex contention while commiting
read only transaction.

https://github.com/alibaba/AliSQL/commit/9baeab74a3bea61abd8b7356b47315f53b92f8e9



 Comments   
Comment by Sergey Vojtovich [ 2016-11-30 ]

plinux, I believe this is backport from InnoDB 5.7. At least we have most of these changes in 10.2 and the rest are not applicable as is. Could you check if there're still anything to merge here?

Comment by Lixun Peng [ 2016-11-30 ]

svoj Weixiang comfirmed if MariaDB merged InnoDB 5.7, then this issue is unnecessary.

Comment by Sergey Vojtovich [ 2016-11-30 ]

Closing per plinux comment.

Generated at Thu Feb 08 07:49:38 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.