Performance Comparison between MyISAM engine and InnoDB engine in MySQL _ MySQL

Performance Comparison between MyISAM engine and InnoDB engine in MySQL table structure

Create table 'myisam '(
'Id' int (11) not null auto_increment,
'Name' varchar (100) default NULL,
'Content' text,
Primary key ('id ')
) ENGINE = MyISAM default charset = gbk;

Create table 'innodb '(
'Id' int (11) not null auto_increment,
'Name' varchar (100) default NULL,
'Content' text,
Primary key ('id ')
) ENGINE = InnoDB default charset = gbk;

Data content:

$ Name = "heiyeluren ";
$ Content = "MySQL supports several storage engines as processors for different table types. The MySQL storage engine includes the engine for processing transaction security tables and the engine for processing non-transaction security tables :? MyISAM manages non-transaction tables. It provides high-speed storage and retrieval, as well as full-text search capabilities. MyISAM is supported in all MySQL configurations. it is the default storage engine, unless you configure MySQL to use another engine by default. ? The MEMORY storage engine provides "in-MEMORY" tables. The MERGE storage engine allows a set to process the same MyISAM table as a separate table. Like MyISAM, MEMORY and MERGE storage engines process non-transaction tables. Both engines are included in MySQL by default. Explanation: The MEMORY storage engine is officially identified as the HEAP engine .? The InnoDB and BDB storage engines provide transaction security tables. BDB is included in the MySQL-Max binary distribution version released for the operating system that supports it. InnoDB is also included in all MySQL 5.1 binary distributions by default. you can configure MySQL to allow or disable any engine as you like .? The EXAMPLE storage engine is a "stub" engine that does not do anything. You can use this engine to create tables, but no data is stored or retrieved from them. The purpose of this engine is to provide a service. in the MySQL source code example, it demonstrates how to start writing a new storage engine. Similarly, it is mainly interested in developers .";

[Insert data-1] (innodb_flush_log_at_trx_commit = 1)
MyISAM 1 W: 3/s
InnoDB, W: 219/s

MyISAM 10 W: 29/s
InnoDB 10 W: 2092/s

MyISAM 100 W: 287/s
InnoDB 100 W: dare not test

[Insert data-2] (innodb_flush_log_at_trx_commit = 0)
MyISAM 1 W: 3/s
InnoDB 1 W: 3/s

MyISAM 10 W: 30/s
InnoDB 10 W: 29/s

MyISAM 100 W: 273/s
InnoDB 100 W: 423/s

[Insert data 3] (innodb_buffer_pool_size = 1024 M)
InnoDB 1 W: 3/s
InnoDB 10 W: 33/s
InnoDB 100 W: 607/s

[Insert data 4] (innodb_buffer_pool_size = 256 M, innodb_flush_log_at_trx_commit = 1, set autocommit = 0)

InnoDB 1 W: 3/s
InnoDB 10 W: 26/s
InnoDB 100 W: 379/s

[MySQL configuration file] (default configuration)

# MySQL Server Instance Configuration File
[Client]
Port = 3306