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

Huge memory pulse in non foreground workload cluster #45966

Closed
winoros opened this issue Aug 10, 2023 · 2 comments · Fixed by #46138
Closed

Huge memory pulse in non foreground workload cluster #45966

winoros opened this issue Aug 10, 2023 · 2 comments · Fixed by #46138
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. sig/planner SIG: Planner type/enhancement The issue or PR belongs to an enhancement.

Comments

@winoros
Copy link
Member

winoros commented Aug 10, 2023

Enhancement

image
We can observe memory pulse periodically.

It's possible that the statistics' async GC causes this.
The following profile is the CPU profile when the memory goes high.
45bbca2f-f52c-4960-a04f-ee5a23124cf2

526e4399-c798-4102-a3ba-6aec34d31d08

@winoros winoros added type/enhancement The issue or PR belongs to an enhancement. sig/planner SIG: Planner labels Aug 10, 2023
@winoros
Copy link
Member Author

winoros commented Aug 10, 2023

There are 99 tables, and each has 100 columns and 12*28 partitions.
No data in them.

@winoros
Copy link
Member Author

winoros commented Aug 10, 2023

It's confirmed that the pulse is caused by GCStats.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. sig/planner SIG: Planner type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants