CMS does not make MySQL cry for you

How much data does MySQL support? In fact, the upper limit of a single MySQL table is mainly related to the maximum file size supported by the operating system. Let's take a look at the official introduction.
1.4.4. Maximum number of MySQL tables
MySQL 3.22 limits the table size to 4 GB. Because the MyISAM storage engine is used in MySQL 3.23, the maximum table size is increased to 65536 TB (2567-1 bytes ). Because the table size is larger, the maximum valid table size of the MySQL database is usually determined by the operating system's limit on the file size, rather than by the MySQL internal limit.
The InnoDB Storage engine saves the InnoDB table in one tablespace, which can be created by several files. In this way, the table size can exceed the maximum capacity of individual files. Tablespaces can include original disk partitions, making it possible for large tables. The maximum tablespace capacity is 64 TB.
The following table lists some examples of operating system file size restrictions. This is only a preliminary guide, not the final one. For the latest information, see the operating system documentation.
MySQL table maximum can be reached: http://dev.mysql.com/doc/refman/5.1/zh/introduction.html#table-size
In fact, the amount of data that MySQL can bear is mainly related to the structure of the data table. It is not a fixed value. When the table structure is simple, the amount of data that can be tolerated is much greater than the complexity of the structure.
According to D. v. according to the results of the evaluation by Team B and the Cmshelp team on the CMS system, a single MySQL table can run well under 10 million records (4 GB, after database optimization, tens of millions of records (10 Gb) run well. So why do some CMS vendors in China still take the responsibility for poor load of their products to MySQL?
This is not fair to MySQL. Instead, those CMS vendors are still adding a lot of fancy features, which eventually leads to a low load on their products. Instead of making corresponding database optimization solutions and standards for their own load results, they continue to retain the complex structure, resulting in endless waste of MySQL resources, in the end, it leads to defects in their load, so they make full use of the traditional advantages of the Chinese -- flexibility: the so-called Table-based storage, although it has mitigated its own load defects to some extent, it has led to a waste of website maintenance and resources. Is this a long-term solution? Although they solved the problem, what about the future? Do you want to achieve the goal through endless table sharding? MYLB. NET. CN bloggers use an inappropriate metaphor to describe the peak pursuit. The tables in MySQL are like a piece of land. A single table is equivalent to using this land to build a high-rise building and fully utilize it to achieve high workload, however, table sharding is equivalent to using this land to build a bungalow. If we want to achieve a high workload, we need to build another ground to achieve our goal, but we need to think about it, however, his ability is insufficient, which makes people feel the waste of resources and the serious defects of planning. Who can use such a CMS system? Is the server configuration constantly changing to make it run well? In most cases, not only such a website exists on a server, so we have to think about whether our pockets are born to meet such a huge small CMS.
For some CMS vendors, MYLB. NET. CN Bloggers can only say that it is extremely irresponsible to push the load problem to MySQL. The table sharding method is to avoid heavy lifting and have no sense of responsibility, this is not only not responsible for yourself, but also for their users. Do you want to mask your product deficiencies by pushing your responsibilities to MySQL and table sharding? It's a big mistake. You can only fool the novice webmasters who are new to website systems and do not know much about source code and databases, but you cannot cheat most people in the circle; it is recommended that such vendors make full use of the time needed to choose from various groups and websites, exaggerate publicity, and slander others, and improve their products to better benefit users; because no matter how many junior webmasters are, the old webmasters will become familiar with source code and databases, and there will be more people who will see your nature at that time.
How many users will CMS vendors be loyal to you? I don't have a sense of responsibility for my own products. How much is left for users? Who dared to choose your product?
In this way, you do not have to think ahead, say you have done one set, and boast that your behavior can only be very high in your own life, but don't forget that you are blowing your own height, the user is the real reviewer, and you have to think about the extent to which you will fall. Thank you for your support for MYLB. NET. CN.