Test the performance of MySQL MyISAM engine and InnoDB Engine

The following articles mainly introduce the performance tests of MySQL MyISAM engine and InnoDB engine. The MyISAM engine and InnoDB engine are often used in actual operations, the following article describes the performance tests of MySQL MyISAM engine and InnoDB engine.

[Hardware configuration]

CPU: AMD2500 + (1.8 GB)

Memory: 1 GB/modern

Hard Disk: 80 GB/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 table types. 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. MySQL 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. Note: The MEMORY storage engine is officially identified as the HEAP engine. · 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, which 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

MySQL 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 
  
  
[mysql]  
  
  
default-character-set=gbk 
  
  
[mysqld]  
  
  
port=3306 
  
  
basedir=”C:/mysql50/”  
  
  
datadir=”C:/mysql50/Data/”  
  
  
default-character-set=gbk 
  
  
default-storage-engine=INNODB 
  
  
sql-mode=”STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION”  
  
  
max_connections=100 
  
  
query_cache_size=0 
  
  
table_cache=256 
  
  
tmp_table_size=50M 
  
  
thread_cache_size=8 
  
  
myisam_max_sort_file_size=100G 
  
  
myisam_max_extra_sort_file_size=100G 
  
  
myisam_sort_buffer_size=100M 
  
  
key_buffer_size=82M 
  
  
read_buffer_size=64K 
  
  
read_rnd_buffer_size=256K 
  
  
sort_buffer_size=256K 
  
  
innodb_additional_mem_pool_size=4M 
  
  
innodb_flush_log_at_trx_commit=1 
  
  
innodb_log_buffer_size=2M 
  
  
innodb_buffer_pool_size=159M 
  
  
innodb_log_file_size=80M 
  
  
innodb_thread_concurrency=8 
 
 

It can be seen that in MySQL 5.0, the performance of MySQL MyISAM and InnoDB Storage engines is not very different. For InnoDB, innodb_flush_log_at_trx_commit is the main option that affects performance. If it is set to 1, therefore, data will be automatically submitted each time it is inserted, resulting in a sharp reduction in performance.

It should be related to refreshing logs. Setting it to 0 can significantly improve the efficiency. Of course, you can submit "set autocommit = 0" in SQL to SET the performance. In addition, I also heard that setting innodb_buffer_pool_size can improve the performance of InnoDB, but I did not find it significantly improved.

Basically, we can consider using InnoDB to replace our MyISAM engine, because InnoDB has many good features, such as transaction support, stored procedures, views, row-level locking, etc, in the case of a lot of concurrency, I believe that InnoDB must be much better than MyISAM. the configuration in cnf is also critical. A good configuration can effectively accelerate your application.

If it is not a complex Web application, but not a key application, you can continue to consider MySQL MyISAM. You can consider the specific situation as needed.