mysql存储引擎memory,ndb,innodb之选择
1 mysql的innodb和cluster的NDB引擎都支持事务,在有共同的特性外,也有不同之处: 以mysql cluster NDB 7.3和MySQL 5.6之InnoDB为例: ndb7.3基于mysql5.6,包括支持innodb1.1,因此可以在cluster里使用innodb表,但这些表不是集群的。 MySQL Cluster NDB存
1
mysql的innodb和cluster的NDB引擎都支持事务,在有共同的特性外,也有不同之处:
以mysql cluster NDB 7.3和MySQL 5.6之InnoDB为例:
ndb7.3基于mysql5.6,包括支持innodb1.1,因此可以在cluster里使用innodb表,但这些表不是集群的。
MySQL Cluster NDB存储引擎用分布式, shared-nothing的架构实现,这使其和innodb有不少不同之处。比如事务、外键、表限制等,具体见下表:
Theseare shown in the following table:
Feature |
|
MySQLCluster |
---|---|---|
MySQLServer Version |
5.6 |
5.6 |
|
|
|
MySQLCluster Version |
N/A |
|
StorageLimits |
64TB |
3TB (Practicalupper limit based on 48 data nodes with 64GB RAM each; can beincreased with disk-based data and BLOBs) |
ForeignKeys |
Yes |
Priorto MySQL Cluster NDB 7.3: No. (Ignored, as with Availablein MySQL Cluster NDB 7.3. |
Transactions |
Allstandard types |
|
MVCC |
Yes |
No |
DataCompression |
Yes |
No (MySQLCluster checkpoint and backup files can be compressed) |
LargeRow Support (> 14K) |
Supportedfor |
Supportedfor (Usingthese types to store very large amounts of data can lower MySQLCluster performance) |
ReplicationSupport |
Asynchronousand semisynchronous replication using MySQL Replication |
Automaticsynchronous replication within a MySQL Cluster. Asynchronousreplication between MySQL Clusters, using MySQL Replication |
Scaleoutfor Read Operations |
Yes(MySQL Replication) |
Yes(Automatic partitioning in MySQL Cluster; MySQL Replication) |
Scaleoutfor Write Operations |
Requiresapplication-level partitioning (sharding) |
Yes(Automatic partitioning in MySQL Cluster is transparent toapplications) |
HighAvailability (HA) |
Requiresadditional software |
Yes(Designed for 99.999% uptime) |
NodeFailure Recovery and Failover |
Requiresadditional software |
Automatic (Keyelement in MySQL Cluster architecture) |
Timefor Node Failure Recovery |
30seconds or longer |
Typically |
Real-TimePerformance |
No |
Yes |
In-MemoryTables |
No |
Yes (Somedata can optionally be stored on disk; both in-memory and diskdata storage are durable) |
NoSQLAccess to Storage Engine |
Nativememcached interface in development (see the MySQL Dev ZonearticleMySQLCluster 7.2 (DMR2): NoSQL, Key/Value, Memcached) |
Yes MultipleAPIs, including Memcached, Node.js/JavaScript, Java, JPA, C++,and HTTP/REST |
Concurrentand Parallel Writes |
Notsupported |
Upto 48 writers, optimized for concurrent writes |
ConflictDetection and Resolution (Multiple Replication Masters) |
No |
Yes |
HashIndexes |
No |
Yes |
OnlineAddition of Nodes |
Read-onlyreplicas using MySQL Replication |
Yes(all node types) |
OnlineUpgrades |
No |
Yes |
OnlineSchema Modifications |
Yes,as part of MySQL 5.6. |
Yes. |
Workload |
|
MySQLCluster ( |
---|---|---|
High-VolumeOLTP Applications |
Yes |
Yes |
DSSApplications (data marts, analytics) |
Yes |
Limited(Join operations across OLTP datasets not exceeding 3TB in size) |
CustomApplications |
Yes |
Yes |
PackagedApplications |
Yes |
Limited(should be mostly primary key access). MySQLCluster NDB 7.3 supports foreign keys. |
In-NetworkTelecoms Applications (HLR, HSS, SDP) |
No |
Yes |
SessionManagement and Caching |
Yes |
Yes |
E-CommerceApplications |
Yes |
Yes |
UserProfile Management, AAA Protocol |
Yes |
Yes |
这两种存储引擎适合的应用场景
Preferredapplication requirements for |
Preferredapplication requirements for |
---|---|
|
|
2
如何选择memory存储引擎或mysql cluster:
When to Use MEMORY or MySQL Cluster.
Developers looking to deploy applications that use the MEMORY storage engine for important, highly available, or frequently updated data should consider whether MySQL Cluster is a better choice. A typical use case for the MEMORY engine involves these
characteristics:
? Operations involving transient, non-critical data such as session management or caching. When the MySQL server halts or restarts, the data in MEMORY tables is lost.
? In-memory storage for fast access and low latency. Data volume can fit entirely in memory without causing the operating system to swap out virtual memory pages.
? A read-only or read-mostly data access pattern (limited updates).
MySQL Cluster offers the same features as the MEMORY engine with higher performance levels, and provides additional features not available with MEMORY:
? Row-level locking and multiple-thread operation for low contention between clients.
? Scalability even with statement mixes that include writes.
? Optional disk-backed operation for data durability.
? Shared-nothing architecture and multiple-host operation with no single point of failure, enabling 99.999% availability.
? Automatic data distribution across nodes; application developers need not craft custom sharding or partitioning solutions.
? Support for variable-length data types (including BLOB and TEXT) not supported by MEMORY.
MEMORY存储引擎和MySQL Cluster的更多细节对比参见白皮书《Scaling Web Services with MySQL Cluster: An Alternative to the MySQL Memory Storage Engine》
Table 15.4 <strong>MEMORY</strong>
Storage Engine Features
Storagelimits |
RAM |
Transactions |
No |
Lockinggranularity |
Table |
MVCC |
No |
Geospatialdata type support |
No |
Geospatialindexing support |
No |
B-treeindexes |
Yes |
T-treeindexes |
No |
Hashindexes |
Yes |
Full-textsearch indexes |
No |
Clusteredindexes |
No |
Datacaches |
N/A |
Indexcaches |
N/A |
Compresseddata |
No |
Encrypteddata[a] |
Yes |
Clusterdatabase support |
No |
Replicationsupport[b] |
Yes |
Foreignkey support |
No |
Backup/ point-in-time recovery[c] |
Yes |
Querycache support |
Yes |
Updatestatistics for data dictionary |
Yes |
[a]Implemented in the server (via encryption functions), ratherthan in the storage engine.
[b]Implemented in the server, rather than in the storage engine.
[c]Implemented in the server, rather than in the storage engine. |
3
myisam, memory, ndb, archive, innodb存储引擎功能汇总:
Table 15.1 StorageEngines Feature Summary
Feature |
MyISAM |
Memory |
InnoDB |
Archive |
NDB |
---|---|---|---|---|---|
Storagelimits |
256TB |
RAM |
64TB |
None |
384EB |
Transactions |
No |
No |
Yes |
No |
Yes |
Lockinggranularity |
Table |
Table |
Row |
Table |
Row |
MVCC |
No |
No |
Yes |
No |
No |
Geospatialdata type support |
Yes |
No |
Yes |
Yes |
Yes |
Geospatialindexing support |
Yes |
No |
Yes[a] |
No |
No |
B-treeindexes |
Yes |
Yes |
Yes |
No |
No |
T-treeindexes |
No |
No |
No |
No |
Yes |
Hashindexes |
No |
Yes |
No[b] |
No |
Yes |
Full-textsearch indexes |
Yes |
No |
Yes[c] |
No |
No |
Clusteredindexes |
No |
No |
Yes |
No |
No |
Datacaches |
No |
N/A |
Yes |
No |
Yes |
Indexcaches |
Yes |
N/A |
Yes |
No |
Yes |
Compresseddata |
Yes[d] |
No |
Yes[e] |
Yes |
No |
Encrypteddata[f] |
Yes |
Yes |
Yes |
Yes |
Yes |
Clusterdatabase support |
No |
No |
No |
No |
Yes |
Replicationsupport[g] |
Yes |
Yes |
Yes |
Yes |
Yes |
Foreignkey support |
No |
No |
Yes |
No |
No |
Backup/ point-in-time recovery[h] |
Yes |
Yes |
Yes |
Yes |
Yes |
Querycache support |
Yes |
Yes |
Yes |
Yes |
Yes |
Updatestatistics for data dictionary |
Yes |
Yes |
Yes |
Yes |
Yes |
[a]InnoDB support for geospatial indexing is available in MySQL5.7.5 and higher.
[b]InnoDB utilizes hash indexes internally for its AdaptiveHash Index feature.
[c]InnoDB support for FULLTEXT indexes is available in MySQL5.6.4 and higher.
[d]Compressed MyISAM tables are supported only when using thecompressed row format. Tables using the compressed row formatwith MyISAM are read only.
[e]Compressed InnoDB tables require the InnoDB Barracuda fileformat.
[f]Implemented in the server (via encryption functions), ratherthan in the storage engine.
[g]Implemented in the server, rather than in the storageengine.
[h]Implemented in the server, rather than in the storageengine. |
要选mysql cluster要根据ndb存储引擎的特征和应用场景做详细测试,安装简测见我的博文《centos65安装简测mysql
cluster 7.3.7》http://blog.csdn.net/beiigang/article/details/43485585
参考
http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster.html
-----------------
blog.csdn.net/beiigang

热AI工具

Undresser.AI Undress
人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool
免费脱衣服图片

Clothoff.io
AI脱衣机

Video Face Swap
使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸!

热门文章

热工具

记事本++7.3.1
好用且免费的代码编辑器

SublimeText3汉化版
中文版,非常好用

禅工作室 13.0.1
功能强大的PHP集成开发环境

Dreamweaver CS6
视觉化网页开发工具

SublimeText3 Mac版
神级代码编辑软件(SublimeText3)

热门话题

MySQL是一种开源的关系型数据库管理系统,主要用于快速、可靠地存储和检索数据。其工作原理包括客户端请求、查询解析、执行查询和返回结果。使用示例包括创建表、插入和查询数据,以及高级功能如JOIN操作。常见错误涉及SQL语法、数据类型和权限问题,优化建议包括使用索引、优化查询和分表分区。

MySQL在数据库和编程中的地位非常重要,它是一个开源的关系型数据库管理系统,广泛应用于各种应用场景。1)MySQL提供高效的数据存储、组织和检索功能,支持Web、移动和企业级系统。2)它使用客户端-服务器架构,支持多种存储引擎和索引优化。3)基本用法包括创建表和插入数据,高级用法涉及多表JOIN和复杂查询。4)常见问题如SQL语法错误和性能问题可以通过EXPLAIN命令和慢查询日志调试。5)性能优化方法包括合理使用索引、优化查询和使用缓存,最佳实践包括使用事务和PreparedStatemen

选择MySQL的原因是其性能、可靠性、易用性和社区支持。1.MySQL提供高效的数据存储和检索功能,支持多种数据类型和高级查询操作。2.采用客户端-服务器架构和多种存储引擎,支持事务和查询优化。3.易于使用,支持多种操作系统和编程语言。4.拥有强大的社区支持,提供丰富的资源和解决方案。

Apache 连接数据库需要以下步骤:安装数据库驱动程序。配置 web.xml 文件以创建连接池。创建 JDBC 数据源,指定连接设置。从 Java 代码中使用 JDBC API 访问数据库,包括获取连接、创建语句、绑定参数、执行查询或更新以及处理结果。

在 Docker 中启动 MySQL 的过程包含以下步骤:拉取 MySQL 镜像创建并启动容器,设置根用户密码并映射端口验证连接创建数据库和用户授予对数据库的所有权限

在 CentOS 上安装 MySQL 涉及以下步骤:添加合适的 MySQL yum 源。执行 yum install mysql-server 命令以安装 MySQL 服务器。使用 mysql_secure_installation 命令进行安全设置,例如设置 root 用户密码。根据需要自定义 MySQL 配置文件。调整 MySQL 参数和优化数据库以提升性能。

优雅安装 MySQL 的关键在于添加 MySQL 官方仓库。具体步骤如下:下载 MySQL 官方 GPG 密钥,防止钓鱼攻击。添加 MySQL 仓库文件:rpm -Uvh https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm更新 yum 仓库缓存:yum update安装 MySQL:yum install mysql-server启动 MySQL 服务:systemctl start mysqld设置开机自启动

MySQL在Web应用中的主要作用是存储和管理数据。1.MySQL高效处理用户信息、产品目录和交易记录等数据。2.通过SQL查询,开发者能从数据库提取信息生成动态内容。3.MySQL基于客户端-服务器模型工作,确保查询速度可接受。
