In most cases, table disassembly is to improve performance, but it increases development complexity and workload. Personally, I think that if the amount of data in a single table is less than one million, there is no need to split it into multiple tables.
In addition, when splitting tables, you will generally feel the characteristics of business data and directly locate the query table instead of multi-table union query, which will make the query efficiency even lower. For example, if the table is split according to the size of the user ID, one table will be split every 100,000, so that after getting the ID, you can directly determine which table to query.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
In most cases, table disassembly is to improve performance, but it increases development complexity and workload.
Personally, I think that if the amount of data in a single table is less than one million, there is no need to split it into multiple tables.
In addition, when splitting tables, you will generally feel the characteristics of business data and directly locate the query table instead of multi-table union query, which will make the query efficiency even lower.
For example, if the table is split according to the size of the user ID, one table will be split every 100,000, so that after getting the ID, you can directly determine which table to query.