Trust MySQL Performance

First, I would like to share my consistent point of view: From a performance perspective, MySQL will not lose to any other database system. If it has any shortcomings, it should mainly be in "functions" and "easy to manage.
 
(The so-called "performance", of course, includes two considerations: "processing speed" and "data volume)
 
Oracle is not a thing but a program written by humans. As a commercial software, what is incomparable is (personal opinion): ComprehensiveFunctionWell-designedManualPowerful and completeManagement tools. (The effect of Oracle's powerful brand image in avoiding decision-making risks in some bureaucratic systems is not a topic in the technical field)
 
Both the manual and management tools can be replaced by the user's diligence and wisdom. "Functions" can be divided into "functional functions" and "performance functions ". (It's a bit difficult, but don't understand it as a function :)
 
Functional features, such as stored procedures, triggers, foreign key constraints, and so on, make it easier to do something during application development. In history, MySQL has been following up slowly. Now it can only be said that it is basically there. As for OLAP, I think it is a dedicated application product instead of the database technology itself.
 
Performance-type features: such as partition, cluster, and internal optimization policies. In these aspects, I think MySQL has done a good job. Although the partitioning function started late, it seems that it is mature because it is not complex and profound. The "optimization policy" should be calculated from the MySQL ManualIn-depth and meticulous. (For example, some file systems support "don't care about the last modification time of Files", and enabling this support can improve hard disk access performance to a certain extent. Even if this is done, are you still worried about what it did not consider ?)
 
If you acknowledge the strong R & D strength of the open-source community, if you think that the R & D team of MySQL is still effective, and if you agree that performance problems are a major target of MySQL, therefore, there is no doubt about the performance potential when MySQL is applied to the production environment.
 
Of course, the potential is the potential. optimization is necessary to realize it.
 
Some people have mentioned that even group by and order by must be done manually. To be honest, RDBMS is doing this. You have to do better than it and it is not easy, unless it is because of the particularity of your data that cannot be expressed by relational databases, your Own Program Logic uses this particularity to achieve high efficiency.
 
In many cases, we feel that the database performance is unsatisfactory because we have not properly optimized it. Presumably many people have had similar experiences: after some seemingly simple optimizations, it is possible to increase the query performance by one or even two orders of magnitude.

 

For the final effect that the optimization work may achieve, I usually judge as follows: Based on the Data's organizational structure and characteristics, I want to get the desired result, is there a logic possibility to achieve the highest efficiency? If there is such a possibility, I basically believe MySQL can do it