Tag - Transaction isolation

Open Source Databases on Big Machines: Does READ COMMITTED Scale on 144 Cores?

READ COMMITTED

In the second post in my series on open source databases on big machines, we’ll look at whether READ COMMITTED scales with multiple cores.
The default transaction level for InnoDB is
REPEATABLE READ. A more permissive level is 
READ COMMITTED, and is known to work well. While the 
REPEATABLE READ level maintains the transaction history up to the start […]

Read more

Introduction into storage engine troubleshooting: Q & A

Overlooked MySQL performance optimization

In this blog, I will provide answers to the Q & A for the “Introduction into storage engine troubleshooting” webinar.
First, I want to thank everybody for attending the July 14 webinar. The recording and slides for the webinar are available here. Below is the list of your questions that I wasn’t able to answer […]

Read more

InnoDB locks and transaction isolation level

Overlooked MySQL performance optimization

What is the difference between InnoDB locks and transaction isolation level? We’ll discuss it in this post.
Recently I received a question from a user about one of my earlier blog posts. Since it wasn’t sent as a comment, I will answer it here. The question:

> I am reading your article:
> https://www.percona.com/resources/technical-presentations/troubleshooting-locking-issues-percona-mysql-webinar
> Full table scan locks […]

Read more