Simple test of MyISAM engine and InnoDB engine performance in MySQL

[Hardware configuration]

cpu:amd2500+ (1.8G)

Memory: 1g/Modern

Hard drive: 80g/ide

[Software configuration]

Os:windows XP SP2

se:php5.2.1

db:mysql5.0.37

Web:iis6

[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 types of tables. The MySQL storage engine includes the engine that handles the transaction security table and the engine that handles the non-transactional security table: · MyISAM Manage non-transaction tables. It provides high-speed storage and retrieval, as well as full-text search capabilities. MyISAM is supported in all MySQL configurations and is the default storage engine unless you configure MySQL to use another engine by default. · The memory storage engine provides an in-memory table. The merge storage engine allows the collection to be processed by the same MyISAM table as a separate table. Like MyISAM, memory and the merge storage engine handle non-transaction tables, both of which are included by default in MySQL. Interpretation: 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 that is released for the operating system that supports it. InnoDB is also included in all MySQL 5.1 binary distributions by default, and you can configure MySQL to allow or disable any engine as you prefer. The example storage engine is a "stub" engine, and it does nothing. You can use this engine to create a table, but no data is stored in or retrieved from it. The purpose of this engine is to serve an example in the MySQL source code, which demonstrates how to start writing a new storage engine. Again, its main interest is for developers. ";

[Insert data-1] (innodb_flush_log_at_trx_commit=1)

MyISAM 1w:3/s

InnoDB 1w:219/s

MyISAM 10w:29/s

InnoDB 10w:2092/s

MyISAM 100w:287/s

InnoDB 100W: not daring to test

[Insert Data-2] (innodb_flush_log_at_trx_commit=0)

MyISAM 1w:3/s

InnoDB 1w:3/s

MyISAM 10w:30/s

InnoDB 10w:29/s

MyISAM 100w:273/s

InnoDB 100w:423/s

[Insert Data 3] (innodb_buffer_pool_size=1024m)

InnoDB 1w:3/s

InnoDB 10w:33/s

InnoDB 100w:607/s

[Insert Data 4] (innodb_buffer_pool_size=256m, Innodb_flush_log_at_trx_commit=1, set autocommit=0)

InnoDB 1w:3/s

InnoDB 10w:26/s

InnoDB 100w:379/s