… user MyISAM most likely will win because of Transactional overhead in Innodb, however if you have large system and many concurrent inserts or parallel long running queries Innodb is likely to be faster because MyISAM has table level locks…
Post: Quick comparison of MyISAM, Infobright, and MonetDB
… statements. I wanted to see how fast MyISAM vs. MonetDB would interpret really large INSERT statements, the kind produced by mysqldump. But… size of the resulting table on disk (smaller is better): MyISAM is 787MB, MonetDB is 791MB, and Infobright is 317MB. Next… “general-purpose” database use — there are a number of limitations (concurrency, for one) and it looks like it’s still fairly…
Post: MySQL Slow query log in the table
… of similar structure with needed index and populate it with insert… select statement as you need it. One little gotcha which… MyISAM, disable concurrent inserts and run long reporting query on the log file query execution is still proceeds. I have not checked if concurrent insert…
Post: High Rate insertion with MySQL and Innodb
… needs high insertion rate for data which generally fits in memory. Last time I worked with similar system it used MyISAM and… to about 15% in MySQL 5.5.8 with 8 concurrent threads. This both shows there is a substantial gains as… your select queries dramatically. The inserts in this case of course are bulk inserts… using single value inserts you would get much lower…
Post: Test Drive of Solid
… for this test. Test 1: Solid, deadlock detection, default (OPTIMISTIC) concurrency control. CREATE TABLE `test2` ( `id` int(11) NOT NULL, `names…: Deadlock detection (deadlock is correctly detected): insert into test2 values (1,’Mysql’),(2,’Solid’),(3,’MyISAM‘); Session1: mysql> begin; Query OK, 0…
Comment: COUNT(*) vs COUNT(col)
… rows since only one transaction executes at any time, because MyISAM does table-level locking. After a transaction commits, it is easy for MyISAM to update the row count for a table (taking into account inserts and deletes done by the… of updates (including deletes and inserts). However, with InnoDB, which uses row-level locking, there are multiple concurrently executing (and as-yet…
Comment: MySQL File System Fragmentation Benchmarks
…_cache_size=8 #*** MyISAM Specific options myisam_max_sort_file_size=100G myisam_max_extra_sort_file_size=100G myisam_sort_buffer_size=185M…_pool_size=304M innodb_log_file_size=152M innodb_thread_concurrency=8 RAM: 1GB Processor: Intel P4 2.253GHz Cache size… for innodb inserts I got 1125, and 1158 inserts per second into the table using myisam I got 1186 and 1177 inserts per second…
Post: MySQL File System Fragmentation Benchmarks
… and does specified number of inserts going to random tables. I used default MySQL settings for MyISAM (table_cache=64) and set… be IO bound. As you can see from MyISAM results (above) the insert speeds does not degrade that badly until going from… from these results – Concurrent growth of many tables causes data fragmentation and affects table scan performance nadly – MyISAM suffers worse than Innodb…
Post: Aligning IO on a hard disk RAID – the Benchmarks
… = 8M bulk_insert_buffer_size = 8M myisam_sort_buffer_size = 8M myisam_max_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover skip-grant… performance up to 15% in case of 8 threads running concurrently. Because the customer was running a database which was way… from the OS perspective is very similar, due to high concurrency response time in the first case is significantly better. It…

