Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TIDB性能问题

Is there a report comparing the performance of a single-node TiDB cluster deployment with MySQL?
Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TIDB性能问题
Is there a report comparing the performance of a single-node TiDB cluster deployment with MySQL?
TiDB on a single machine can’t outperform MySQL; you can test it yourself.
Is there any official conclusion or report? The test results show a difference of 3-4 times, and I need to report it.
Or should I deploy multiple TiKV instances on a single server? Would that be useful?
A single machine can’t outperform MySQL. I remember someone in the community did an experiment on this.
Unless you have multiple NVMe physical drives, with each TiKV pointing to a separate physical drive, the speed will significantly improve.
By design, TiDB is not meant to run on a single machine, so this comparison is meaningless.
There’s no need to compare, it’s meaningless. TiDB on a single machine definitely can’t compete with MySQL.
Comparing single machines is not very meaningful. You can refer to the image below:
TiDB VS MySQL Performance - Alibaba Cloud Developer Community (aliyun.com)
Single-node deployment is generally used for testing functionality.
If you can only compare on a single machine, it is recommended to deploy TiDB on a single node and then test after the data volume of a single table rises to over hundreds of millions. With small data volumes, MySQL will definitely have the advantage.
The current usage scenario involves 210,000 data tables, with only a few rows of data per table. Previously, MySQL was used, but now we are adapting to the TiDB database for localization. The deployment method is to deploy each component on a single server. The current test conclusion is that the performance is significantly worse than MySQL. I would like to see if there are any official conclusions.
For tables with only a few rows of data, you can try small table caching.
However, given your description, it seems like using Redis might be better since each table only has a few rows of data.
Currently, I have deployed TiDB on a single server, and it takes about 180ms to create a single table. The same table in MySQL only takes 20ms. Is this difference normal, and is there any way to improve the table creation speed?
How many TiKVs do you have? Try deploying just one on a single machine.
Can I ask about the server configuration? Additionally, I suggest deploying a single instance with 1 TiDB, 1 PD, and 1 TiKV.
Executing a single SQL in a distributed system is definitely slower than on a single machine, as each component needs to go through network calls.
Are there any optimization solutions? Currently, only a single server is allowed, and the time difference compared to MySQL table creation is too large. Are there any configuration changes that can improve this speed?