Performance with large number of tables using TiFlash #66441
sykp241095
started this conversation in
Migrated from Forum
Replies: 2 comments
-
|
Original author: dveeden I would expect a small performance degradation and not a grinding halt. There some steps you can take to deal with this like using more powerful hardware for PD or otherwise give more resources to it. With TiFlash you often don’t need to put all tables on TiFlash, which can help to reduce the total number of tables in TiFlash. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Original author: gmkt Great, thanks for the insights. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Original author: gmkt
Original time: 2023-04-14 19:03:08.223757
Original ID/Slug: 534 / performance-with-large-number-of-tables-using-tiflash
Application environment:
PoC
TiDB version:
7.0
Reproduction method:
N/A
Problem:
The docs (Create TiFlash Replicas | PingCAP Docs) say “It is recommended that you do not replicate more than 1,000 tables because this lowers the PD scheduling performance. This limit will be removed in later versions.”
I’m wondering how significant the impact is, particularly as the number of tables grows well beyond that limit (say 10k - 30k tables of all sizes from 0 K to 200 G).
Are we talking 5% - 10% slower or grinding to a halt? I’m just looking for a guess based on other peoples experiences since I’m sure it will vary based on dataset, hardware, topology, etc.
Any info / update / timeline on removing or lessening that impact?
Thanks!
Resource allocation:
Servers have 12 cores, 64 GB of RAM, and 4 TB NVME SSDs.
Attachment:
Beta Was this translation helpful? Give feedback.
All reactions