InnoDB vs MyISAM vs Falcon benchmarks

核心提示： `id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT,`name` varchar(64) NOT NULL DEFAULT '',`email` varchar(64) NOT NULL DEFAULT '',`pas

`id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT,

`name` varchar(64) NOT NULL DEFAULT '',

`email` varchar(64) NOT NULL DEFAULT '',

`password` varchar(64) NOT NULL DEFAULT '',

`dob` date DEFAULT NULL,

`address` varchar(128) NOT NULL DEFAULT '',

`city` varchar(64) NOT NULL DEFAULT '',

`state_id` tinyint(3) UNSIGNED NOT NULL DEFAULT '0',

`zip` varchar(8) NOT NULL DEFAULT '',

`country_id` smallint(5) UNSIGNED NOT NULL DEFAULT '0',

PRIMARY KEY (`id`),

UNIQUE KEY `email` (`email`),

KEY `country_id` (`country_id`,`state_id`,`city`)

)

In this benchmark we used only read (SELECT) queries with different typical data access patterns:

primary key single row lookup, primary key range lookup, same access types for primary key and full table scans.

To highlight different properties of storage engines we tested ranges with and without LIMIT clause, and tested queries which

need to read the data or can only be satisfied by reading the index.

This benchmark is so called "micro" benchmark which concentrates on particular simple storage engine functions and we use it to see performance and scalability in this simple cases. We also use CPU bound workload in this case (no disk IO) to see how efficient storage engines are in terms of CPU usage. In real life workload results are likely to be very different.