Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query statistics lock is consuming excessive CPU resources during the auto-analysis check #49472

Closed
hi-rustin opened this issue Dec 14, 2023 · 2 comments · Fixed by #49473
Closed
Labels
affects-7.5 found/customer Customers have encountered this bug. severity/moderate sig/planner SIG: Planner type/bug This issue is a bug.

Comments

@hi-rustin
Copy link
Member

Enhancement

If you have a large number of tables, the auto-analyze worker can help you analyze them efficiently by checking if they need to be analyzed. However, during the analysis, we need to obtain the stats lock information. If a table is already locked, then there is no need to analyze it.
If your table is small, it needs to be checked frequently which can lead to excessive CPU resource consumption due to the querying of statistics lock.

img_v3_0062_98257775-ab90-4ea8-bbf9-64252d65b53g

@seiya-annie
Copy link

/found customer

1 similar comment
@seiya-annie
Copy link

/found customer

@ti-chi-bot ti-chi-bot bot added the found/customer Customers have encountered this bug. label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.5 found/customer Customers have encountered this bug. severity/moderate sig/planner SIG: Planner type/bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants