mysql的innodb和myisam的dml效能對比
C:\Users\ibm>mysql -uroot -proot
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 22
Server version: 5.5.17 MySQL Community Server (GPL)
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 22
Server version: 5.5.17 MySQL Community Server (GPL)
Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> use test
通過下面的對比,發現myisam的dml效率高於innodb,但是在
併發環境下,myisam的表鎖導致其dml效能差於innodb。
insert into test_innodb select * from data;
(2621440 row(s) affected)
Execution Time : 00:01:46:392
Transfer Time : 00:00:00:000
Total Time : 00:01:46:392
insert into test_myisam select * from data;
(2621440 row(s) affected)
Execution Time : 00:00:18:985
Transfer Time : 00:00:00:000
Total Time : 00:00:18:985
併發環境下,myisam的表鎖導致其dml效能差於innodb。
insert into test_innodb select * from data;
(2621440 row(s) affected)
Execution Time : 00:01:46:392
Transfer Time : 00:00:00:000
Total Time : 00:01:46:392
insert into test_myisam select * from data;
(2621440 row(s) affected)
Execution Time : 00:00:18:985
Transfer Time : 00:00:00:000
Total Time : 00:00:18:985
update test_innodb set c='100';
(2621440 row(s) affected)
Execution Time : 00:02:13:475
Transfer Time : 00:00:00:000
Total Time : 00:02:13:475
Execution Time : 00:02:13:475
Transfer Time : 00:00:00:000
Total Time : 00:02:13:475
update test_myisam set c='300';
(2621440 row(s) affected)
Execution Time : 00:00:48:626
Transfer Time : 00:00:00:000
Total Time : 00:00:48:626
(2621440 row(s) affected)
Execution Time : 00:00:48:626
Transfer Time : 00:00:00:000
Total Time : 00:00:48:626
delete from test_innodb;
(2621440 row(s) affected)
Execution Time : 00:01:13:476
Transfer Time : 00:00:00:000
Total Time : 00:01:13:476
Execution Time : 00:01:13:476
Transfer Time : 00:00:00:000
Total Time : 00:01:13:476
delete from test_myisam
(2621440 row(s) affected)
Execution Time : 00:00:00:124
Transfer Time : 00:00:00:000
Total Time : 00:00:00:124
(2621440 row(s) affected)
Execution Time : 00:00:00:124
Transfer Time : 00:00:00:000
Total Time : 00:00:00:124
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/20625855/viewspace-765356/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- MySQL三種InnoDB、MyISAM和MEMORY儲存引擎對比MySql儲存引擎
- 資料庫系列:MySQL引擎MyISAM和InnoDB的比較資料庫MySql
- Mysql 中 MyISAM 和 InnoDB 的區別MySql
- MyISAM與InnoDB兩者的區別、詳細總結、效能對比
- MySQL儲存引擎:MyISAM和InnoDB的區別MySql儲存引擎
- mysql 的myisam和innodb對應的cache管理方式的一點差異MySql
- MySQL 中 MyISAM 中的查詢為什麼比 InnoDB 快?MySql
- MySQL中MyISAM為什麼比InnoDB查詢快MySql
- MySQL儲存引擎簡介及MyISAM和InnoDB的區別MySql儲存引擎
- MySQL中myisam和innodb有什麼差異?MySql
- TIDB和MySQL效能對比TiDBMySql
- mysql innodb 主鍵INT、BIGINT、VARCHAR併發插入效能對比MySql
- MySQL之儲存引擎InnoDB和MyISAM的區別及底層詳解MySql儲存引擎
- 說說自己對於 MySQL 常見的兩種儲存引擎:MyISAM與 InnoDB的理解MySql儲存引擎
- MySQL儲存引擎--MyISAM與InnoDB區別MySql儲存引擎
- MySQL兩種儲存引擎: MyISAM和InnoDB 簡單總結MySql儲存引擎
- MyISAM InnoDB 區別
- 使用MyISAM表和InnoDB的一些記錄GD
- MySQL:Innodb 關於Handler_commit每次DML增加2的原因MySqlMIT
- MySQL常見的兩種儲存引擎:MyISAM與InnoDB的愛恨情仇MySql儲存引擎
- 十八、Mysql儲存引擎並不只有MyISAM、InnoDB——精髓MySql儲存引擎
- 總結MySQL儲存引擎MyISAM與InnoDB區別MySql儲存引擎
- KunlunDB對MySQL私有DML語法的支援MySql
- MySQL的DDL和DML操作語法MySql
- MySQL 中的 distinct 和 group by 的效能比較MySql
- MySQL的索引為什麼用B+Tree?InnoDB的資料儲存檔案和MyISAM的有何不同?MySql索引
- mysql myisam的鎖機制MySql
- MySQL alter 新增列對dml影響MySql
- Go 和 Java 的效能對比,真的如此嗎?GoJava
- MySQL優化篇系列文章(二)——MyISAM表鎖與InnoDB鎖問題MySql優化
- MySQL中InnoDB引擎對索引的擴充套件MySql索引套件
- MYSQL引擎的鎖對比MySql
- 服務端指南 資料儲存篇 | MySQL(02) 儲存引擎的 InnoDB 與 MyISAM 之爭服務端MySql儲存引擎
- Mobx 與 Redux 的效能對比Redux
- C# 單例模式的實現和效能對比C#單例模式
- mysql常用儲存引擎(InnoDB、MyISAM、MEMORY、MERGE、ARCHIVE)介紹與如何選擇MySql儲存引擎Hive
- python date 和 datetime 的取值範圍(對比 Mysql 的 datetime 和 timestamp)PythonMySql
- Flutter和原生應用效能對比Flutter
- Django和Fastapi非同步效能對比DjangoASTAPI非同步