-
Notifications
You must be signed in to change notification settings - Fork 411
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
Memory tracker is not accurate if read pool is enabled. #8128
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.
component/storage
severity/major
type/bug
The issue is confirmed as a bug.
Comments
/severity major |
windtalker
added
affects-6.5
This bug affects the 6.5.x(LTS) versions.
affects-7.1
This bug affects the 7.1.x(LTS) versions.
and removed
may-affects-6.5
may-affects-7.1
labels
Sep 21, 2023
12 tasks
This was referenced Sep 25, 2023
12 tasks
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.
component/storage
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
The test.sql is
With read pool disabled, the concurrency is 2, the memory usage reported by memory tracker are
With read pool disabled, the concurrency is 1, the memory usage reported by memory tracker are
With read pool enabled, the concurrency is 2, the memory usage reported by memory tracker are
With read pool disabled, the concurrency is 1, the memory usage reported by memory tracker are
As we can see, when read pool enabled, when running queries with concurrency(even the concurrent is only 2), the memory usage reported by memory tracker is very inaccurate, for both query level and global level.
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)
The text was updated successfully, but these errors were encountered: