My Oracle Support Banner

With many concurrent transactions (e.g., 4500), accessing the performance_schema.data_locks and data_lock_waits table has a significant CPU, memory, disk(swap), and performance impact. (Doc ID 2988370.1)

Last updated on DECEMBER 11, 2024

Applies to:

MySQL Server - Version 8.0 and later
Information in this document applies to any platform.

Symptoms

With many concurrent transactions (e.g., 4500), accessing the performance_schema.data_locks and data_lock_waits table has a significant CPU, memory, disk(swap), and performance impact.
Queries that use data_lock and data_lock_waits with JOINs other tables are more performance impacted.
For example, queries such as sys.innodb_lock_waits and the following query.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.