MySQL：建议行数 [英] MySQL: Advisable number of rows

问题描述

考虑具有7列的索引MySQL表，不断查询并写入。在将数据分解为其他表格之前，可以通过将数据分解为性能来改善表格应该允许包含哪些行的可取数量？

解决方案

是否通过分割数据获得性能，取决于您将在其上运行的数据和查询。您可以在表中存储数百万行，并具有良好的索引和精心设计的查询，它仍将是超级快速。如果您已经确信您的索引和查询与其可以一样好，那么只考虑分区，因为它可能比其价值更麻烦。

Consider an indexed MySQL table with 7 columns, being constantly queried and written to. What is the advisable number of rows that this table should be allowed to contain before the performance would be improved by splitting the data off into other tables?

解决方案

Whether or not you would get a performance gain by partitioning the data depends on the data and the queries you will run on it. You can store many millions of rows in a table and with good indexes and well-designed queries it will still be super-fast. Only consider partitioning if you are already confident that your indexes and queries are as good as they can be, as it can be more trouble than its worth.

这篇关于MySQL：建议行数的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！