Original link: https://mariadb.com/kb/en/mariadb-vs-mysql-features/
Xiaomo translation------
Support for more storage engines
In addition to the standard MyISAM, blackhole, CSV, memory, and ARCHIVE, the following storage engines are also included in the MARIADB source and the binary package:
- Aria
- XtraDB (can be used to replace InnoDB)
- PBXT (included in MariaDB 5.1, MariaDB 5.2 and MariaDB 5.3. is disabled in MariaDB 5.5)
- Federatedx (can be used to replace federated)
- Oqgraph (included in MariaDB 5.1, MariaDB 5.2 and MariaDB 5.3. In MariaDB 5.5 disabled) -added to version 5.2
- Sphinxse -Added to version 5.2
- Ibmdb2i. Oracle removed it from MySQL 5.1.55, but we kept it to the 5.5 version in MARIADB.
- The Cassandra in MariaDB-10.0
- We are working on adding other no-sql-type storage engines to mariadb.
The speed increase
- MariaDB 5.3 Adds a lot of optimization and enhancement features. The subquery is now finally available! A complete list and a comparison with MySQL can be found here. You can find the baseline information here.
- Faster and more secure replication: Group commit for the binary log. This allows many settings and updates to replicate more than twice times faster.
- InnoDB's Asynchronous IO subsystem performance has improved on Windows systems.
- MEMORY (HEAP) engine index is faster. According to a simple test result, the insert operation in an integer index is about 24% faster than MySQL, and the insert operation on the char (20) column is 60% faster.
- CHECKSUM table runs faster.
- We improved the performance of the character set transformation (and removed the operation when the conversion was not required). In general the speed can be increased by 1-5 (according to the Sql-bench test), but the character set between 0x00-0x7f should have a better effect.
- Pool of Threads in MariaDB 5.1 good, especially in MariaDB 5.5. You can use more than 200,000 connections when running MARIADB, while showing significant speed gains over a large number of connections.
- The Dbug feature also has several performance optimizations that allow for faster execution when compiling and debugging without using debugging.
- The use of the ARIA storage engine makes complex queries perform faster (general query operations use disk-based temporary tables). Aria is typically applied to internal temporal tables, allowing complex queries to increase execution speed. The temporary table is accessed faster than Myisam,aria, thanks to Aria's caching of row data in memory and, typically, the need to write temporary rows to disk.
- Expanded the test suite. Now even if you want to test more content, the speed is faster than before.
Expand & New Features
We've added a lot of new features to MARIADB. If a patch or feature is effective, safe and stable, we will try to add it to mariadb. The most notable new features are as follows:
- Microseconds in MariaDB -added to 5.3
- Microsecond Precision in Processlist
- Table Elimination
- Virtual Columns -Added to 5.2
- Extended User Statistics -Added to 5.2
- Segmented Key Cache -Added to 5.2
- KILL all queries for a user -added to 5.3
- Pluggable authentication -added to 5.2
- Storage-engine-specific CREATE TABLE -Added to 5.2
- Enhancements to Information SCHEMA. PLUGINS table -Added to 5.2
- Group commit for the binary log. This significantly speeds up the replication speed -added to 5.3
- Add
--rewrite-db
ALTER TABLEAndLOAD DATA INFILE操作的Progress reporting. — 新增于5.3- Faster joins and subqueries. -Added to 5.3
- Handlersocket and faster handler calls. -Added to 5.3
- Supports dynamic Columns. -Added to 5.3
- GIS functionality -added to 5.3
- Multi-Source replication. -Added to 10.0
- SHOW EXPLAIN Gets the EXPLAIN plan in the other thread that is performing the query operation. -Added to 10.0
You can refer to features for each release to get a more detailed list of features.
Better performing Tests
- There are more test cases in the test suite.
- Test for potential bug fixes.
- Build tests with different configuration options to get better test features.
- Remove the invalid test. (e.g. if a feature point is not built in the test, it will not be used for testing.)
Fewer warnings and errors
- Bugs is not a good thing. Fix the bugs as much as possible and raise new problems with less effort.
- Compiling a warning is not a good thing either. The compilation warning has been restricted as much as possible.
The real Open source
- The release of the MARIADB code complies with the GPL, LPGL or BSD protocol. MARIADB does not have a closed-source module like the MySQL Enterprise Edition. In fact, the closed source module code in MySQL 5.5 Enterprise Edition can be found in the MARIADB open source version.
- MARIADB contains test cases for all bugs that have been fixed. Oracle does not provide test cases that MySQL5.5 newly fixed bugs.
- All the bugs and development plans are public.
- Adhering to the spirit of true open source, MARIADB is continuously developed and maintained by the community.
RELATED LINKS
Reference compatiblity between MariaDB and MySQL
- Previous article "MariaDB" MariaDB vs MySQL-compatibility
- Next "MariaDB" installs MariaDB, coexists with MySQL
-
Top
-
1
-
Step
-
0
"MariaDB" MariaDB vs MySQL-Features
