If you had a Sailor Moon magic wand that could instantly improve the TiDB cluster, what problem would you most want to solve?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 给你一支美少女战士的魔法棒，能马上让 TiDB 集群变得更好，你最希望能解决什么问题？

| username: Jellybean

Some time ago, I posted a topic What is the main reason for your technical selection from MySQL to TiDB? to understand why the community experts chose TiDB.

Now, I would like to know if any of you have encountered pain points or urgent issues that need to be resolved while using TiDB, or if there are any new features you hope to see added to make TiDB more complete.

Is it too many large SQL queries causing frequent memory OOM?

Is the execution plan inaccurate, causing the business to suddenly slow down and become a headache?

Feel free to continue sharing your complaints and let us know what aspects of using TiDB are not satisfactory and what features need to be improved or added.

2
| username: Jellybean | Original post link

For deep users of HTAP, we hope the multi-tenant feature continues to improve, enabling resource management for memory.

3
| username: dba远航 | Original post link

Based on MySQL databases, distributed issues include: limited functionality support (views, stored procedures, etc.), suboptimal performance for large SQL operations, and execution plan deviations.

4
| username: Kongdom | Original post link

100% stable operation :yum: unattended

5
| username: 小龙虾爱大龙虾 | Original post link

Alright, you can pack up and go home :grinning:

6
| username: Kongdom | Original post link

:yum: Sorry, I’m a developer~ Hahaha

7
| username: TiDBer_jYQINSnf | Original post link

The cluster performance is stable without any glitches.

8
| username: DBAER | Original post link

Enhance multi-tenant functionality and strengthen the optimizer for complex SQL.

9
| username: 哈喽沃德 | Original post link

We need functions and stored procedures.

10
| username: xfworld | Original post link

Hurry up and stabilize TiCDC… This is currently the biggest pain point in integration.

11
| username: Fly-bird | Original post link

Automatically optimize slow SQL

12
| username: Jellybean | Original post link

Haha, this is interesting.

100% stable operation, there will be no more TiDB DBAs in the world. In the future, by introducing AI DBAs, it might get infinitely closer.

13
| username: Kongdom | Original post link

:+1: Reliable

14
| username: TiDBer_5Vo9nD1u | Original post link

There are quite a lot of parameters.

15
| username: TiDBer_08RNElU3 | Original post link

It can automatically optimize parameters.

16
| username: onlyacat | Original post link

Peripheral tools
Stability
Forward compatibility

17
| username: TiDBer_vfJBUcxl | Original post link

Automatically optimize slow SQL

18
| username: 随便改个用户名 | Original post link

Automatically diagnose the current abnormal SQL and automatically identify the SQL that caused the service to crash. Sometimes it feels quite troublesome to manually find out which SQL caused the TiDB anomaly.

19
| username: TiDBer_小阿飞 | Original post link

Automatic tuning tools & zero-downtime switching & CAP :joy: