- 论坛徽章:
- 0
|
MySQL storage engines
One of the big advantages of MySQL is its concept of "pluggable storage engines". This means you can choose the most optimal storage engine for your needs. This also has a disadvantage: You have to know what you are doing...
MySQL provides the following storage engines:
mysql> SHOW ENGINES;
+------------+----------+-------------------------------------------------------+
| Engine | Support | Comment |
+------------+----------+-------------------------------------------------------+
| MyISAM | DEFAULT | Default engine with great performance |
| MEMORY | YES | Hash based in memory tables |
| InnoDB | YES | Transactional storage engine with row-level locking |
| Falcon | YES | Falcon storage engine |
| BerkeleyDB | NO | Transactional storage engine with page-level locking |
| BLACKHOLE | YES | /dev/null storage engine for replication transmission |
| EXAMPLE | YES | Example storage engine |
| ARCHIVE | YES | Archive storage engine |
| CSV | YES | CSV storage engine |
| ndbcluster | DISABLED | Clustered, fault-tolerant, memory-based tables |
| FEDERATED | YES | Federated MySQL storage engine (like database links) |
| MRG_MYISAM | YES | Collection of identical MyISAM tables (MERGE) |
| ISAM | NO | Obsolete storage engine |
+------------+----------+-------------------------------------------------------+
There are also some independent storage engine providers:
solidDB
PrimeBase XT
OpenOLAP
Thinking Networks Storage Engine
RitmarkFS
FS map to mysql
Sphinx Search
mdbtools storage engine
Distributed Data Engine
MemCacheD Storage Engine (by Brian Aker)
RRD Storage engine (insider information, unofficial name, not yet available). A work around you can find here: Round-Robin Database Storage Engine (RRD)
VEMySQL Velocity Storage Engine
NitroEDB
InfoBrigth
FIFO storage engine (Domas)
Amazon S3 storage engine
ScaleDB |
|