Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 提问关于tidb类型的选择
[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
7.5
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]
We are using AWS hosts.
I noticed that their KV selected EBS with a speed limit of 120MB for 3 TiKV. If there are a lot of read and write operations, will the speed be throttled?
It feels too low for TiKV.
This speed is like a mechanical hard drive.
The mechanical disk has a write speed of 250MB/s.
Not even as good as a mechanical drive 
This configuration cannot bring out the performance of the database.
If the TiKV memory is large enough, it should be able to manage.
If you don’t use high-performance disks for TiKV nodes in TiDB, it will be very problematic later on…
In a production environment, TiKV machines should all be NVMe, right? If it’s a small system with low concurrency, just use a regular MySQL.
Performance is even worse than a mechanical disk, probably fatal.
This disk latency configuration is quite eye-catching.
This performance definitely won’t cut it, it might even be worse than a laptop.
It should be very slow, TiDB has high IO requirements.