CMS don't let Mysql cry for you _mysql

So how much is the amount of data that MySQL can 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.
1.4.4. What is the maximum number of MySQL tables to achieve?
The MySQL 3.22 limit table size is 4GB. The maximum table size was increased to 65536TB (2567–1 bytes) due to the use of the MyISAM storage engine in MySQL 3.23. Because of the larger size of the table allowed, the maximum valid table size of the MySQL database is usually determined by the operating system's limitations on file size, rather than the internal limits of MySQL.
The InnoDB storage engine saves the InnoDB table in a table space that can be created by several files. This allows the table size to exceed the maximum capacity of the individual file. Table spaces can include raw disk partitions, making it possible to make large tables. The maximum capacity of the table space is 64TB.
In the following table, some examples of operating system file size limits are listed. This is only a preliminary guide, not a final one. For the latest information, refer to the documentation for the operating system.
MySQL table maximum can achieve how much: http://dev.mysql.com/doc/refman/5.1/zh/introduction.html#table-size
In fact, the amount of data that MySQL can withstand is mainly related to the structure of the datasheet, not a fixed number. The structure of the table is simple, the amount of data that can withstand is relatively larger than the structure of the complex.
According to the D.V.B team and the CMSHELP team to do the CMS system evaluation results, the MySQL single table generally in 20 million records (4G) under the good operation, after the optimization of the database after 50 million records (10G) running well. Then why some of the domestic CMS manufacturers will also be their own product load poor responsibility to the MySQL?
This is not fair for MySQL, those CMS vendors instead of doing the kernel do not do it is still adding a lot of fancy features, eventually resulting in the product itself too low load. They did not make the corresponding database optimization plan and standard for their own load effect, but continue to retain the complex structure of the resources of MySQL endless waste, resulting in its load of defects, so they give full play to the Chinese traditional advantages-adaptation: The use of the so-called sub-table storage , although to some extent alleviate the shortcomings of their own load, but led to the site maintenance and waste of resources, is this a long-term solution? Although they solved the immediate problem, but later? Do you want endless tables to achieve your goals? MYLB.NET.CN the main Chase peak with an improper analogy to describe, the table in MySQL is like a piece of land, the single table is equivalent to the use of the cover of high-rise building to make full use of high personnel load, but the table is equivalent to using this piece of land built a cottage, if in order to achieve high personnel load, then need to open the land to achieve the purpose, But we have to think, is not enough, or his ability is not enough, so that people feel the waste of resources and planning a serious flaw. So for such a CMS system, who dares to use? Is it necessary to change the server configuration endlessly in order to make it run well? And most of the case of a server is not only such a site, then we have to think about whether our purse is to meet such a large small CMS and health.
For some CMS vendors, MYLB.NET.CN Bo can only say that its load problem to the MySQL body is the practice is extremely irresponsible behavior, the approach of the table is evasive approach, not only is not responsible for their own, but also for their users irresponsible behavior, Do you want to use the responsibility to the MySQL and the list of practices to cover up the shortcomings of their products? It's a big mistake, you can only fool those who just catenary station system for the source code and the database is not familiar with the novice webmaster, but for most insiders you can not deceive; it is recommended that such manufacturers or to all groups and sites to provoke right and wrong, exaggerated publicity, A lot of time to denigrate others to improve their products so that users better benefit from it, because no matter how the primary webmaster will have become old webmaster to the source and database at ease, then see your essence of the people will be more.
How many users will be loyal to the CMS vendors who are so irresponsible? There is no sense of responsibility for their products, so how much do you have left to treat users? Who else dares to choose your product?
So do not think enterprising, said a set to do, boasting their own behavior can only be a very high, but do not forget that your height is blown up, the user is the real critic, then you will fall to what extent it will be their own thinking. Thank you for your support for MYLB.NET.CN.