How much data does MySQL support?

MySQL is a popular database for small and medium-sized websites, however, many people do not know exactly how much data MySQL can support, coupled with some domestic CMS manufacturers to the responsibility of the data load to it, resulting in a lot of owners do not understand the MySQL has a lot of misunderstanding it, then, How much does MySQL data amount to support? In fact, the upper limit of MySQL single table, mainly related to the maximum file size supported by the operating system. Let's take a look at the official introduction.

What is the maximum number of MySQL tables to reach? MySQL 3.22 limits the table size to 4GB. Since the MyISAM storage engine was used in MySQL 3.23, the maximum table size was increased to 65536TB (2567–1 bytes). Due to the larger table size allowed, the maximum valid table size for MySQL database is usually determined by the operating system's limit on file size, rather than the MySQL internal limit. The InnoDB storage engine saves the InnoDB table in a table space, which can be created by several files. In this way, the size of the table can exceed the maximum capacity of the individual file. Table spaces can include raw disk partitions, making large tables possible. The maximum capacity of a tablespace is 64TB.

In fact, the amount of data that MySQL can withstand is largely related to the structure of the data sheet, not a fixed number. The structure of the table is simple, then the amount of data can withstand more complex than the structure of the larger.

According to D.V.B team and Cmshelp team to do CMS system evaluation results, MySQL single table about 20 million records (4G) can run well, after the optimization of the database 50 million records (10G) run well. So why do some domestic CMS manufacturers will also be the responsibility of their products load poor to MySQL it?

This is not fair to MySQL, those CMS manufacturers instead of the kernel does not do but still add a lot of fancy features, resulting in the product itself is too low load. They do not have a corresponding database optimization scheme and standards for their own load effect, but continue to maintain a complex structure resulting in the endless waste of MySQL resources, resulting in their load defects, so they give full play to the Chinese traditional advantages-------cop's use of the so-called sub-table storage , although to some extent alleviate the shortcomings of their own load, but led to the maintenance of the site and the waste of resources, is this a permanent one? Although they solved the immediate problem, but later? Do you want an endless scale to achieve your goal?

With an inappropriate analogy, the table in MySQL is like a piece of land, a single table is equivalent to the use of the ground cover high-rise buildings to maximize the use of higher personnel load, but the table is equivalent to using this land to cover a cottage, if in order to achieve high personnel load that would require another open ground to achieve the purpose, but we have to think is not enough, or his ability is not enough, so the practice makes people feel the waste of resources and planning serious shortcomings.

So for such a CMS system, who dares to use? Do you want to change the server configuration endlessly in order to make it run well? Moreover, most of the cases of a server is not the only such a site, then we have to think about whether we are to meet such a large small CMS and pay.

Some CMS manufacturers are advised to improve their products, so that users benefit better. Otherwise, who dares to choose your product?

How much data does MySQL support?