MySQL aims for speed_PHP Tutorial

MySQL aims for speed
------------------------------------------------ ---------------------------------------------
MySQL and PostgreSQL are both very famous databases Open source projects have a tendency to replace commercial database systems, but they have different design goals. Generally speaking, if you need faster speed, you can give priority to MySQL, and if you need some new features, you can choose PostgreSQL.
MySQL is currently maintained by MySQL AB. Its latest stable version is 3.23. The 3.23Max version that supports transaction processing has also entered the Beta testing stage, and its latest development version 4.0 has entered the Alpha testing stage. It's easy to be impressed by its slightly unusual licensing fee. Its price changes depending on the platform and installation method. Its Windows version is not free in any case, while for any Unix/Linux version, if the user or system administrator installs it himself, it is free, and third-party installation must be paid. Licensing Fees.
MySQL is a network database management system based on C/S architecture. It is designed with speed as the main goal. It can quickly handle query requests from multiple users. It is also very fast when processing client connections. It is very suitable for use as the backend database of a Web site. Relatively speaking, PostgreSQL's execution speed is relatively slow. It generates a child process for each connection, and the steps of generating child processes and establishing background service processes slow down its execution speed. MySQL's server functions are very compact, and various complex functional processing (such as XML support) are completely placed on the client, which allows adding functions without sacrificing the speed and reliability of the database server. Moreover, it has been proven by commercial memory detection programs that there are no memory leaks. Continuous interruptions and program crashes are also rare. It is more stable than PostgreSQL.
In the initial design stage, MySQL was mainly aimed at medium-sized databases, that is to say, the size of the database was about tens of millions of rows, and each table was about 100MB. With the development of the MySQL project, its use areas have gradually expanded to the fields of large terabyte-scale databases and small handheld or embedded devices. But in the short term, MySQL will not support real-time databases or large-scale cluster databases. Although in its 3.23 version, it enables the system to theoretically support 8000PB tables through MyISAM tables. However, due to operating system limitations, under most Linux systems, it can only handle tables up to 2GB or 4GB. In version 3.23, new features such as support for replication of large server clusters, InnoDB transaction table processor, Berkeley DB transaction table processor interface, full-text search, MyODBC 2.5 interface, automatic checking and repair of MyISAM tables, and batch inserts are also added. module.
The introduction of InnoDB and BDB transaction table processors enables data tables stored in these methods in MySQL to have good transaction processing capabilities. However, for tables stored in other ways, there is usually some performance penalty when using atomic operations to maintain integrity and consistency. LOCK TABLES can be used for table locking when integrity is important. Starting from 3.23.44, InnoDB tables support foreign code restriction checking, but its use, especially the misuse of foreign codes, may cause serious problems.

http://www.bkjia.com/PHPjc/631142.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/631142.htmlTechArticleMySQL aims at speed------------------ -------------------------------------------------- ----------- MySQL and PostgreSQL are both very famous database open source projects, and both...