…. MyISAM does not maintain checksum consistency during regular operations and is not ACID compliant. MyISAM and InnoDB may perform differently under concurrency, which this benchmark does not cover. I will make a follow-up post about concurrency…
Post: MyISAM concurrent insert
June 13, 2006 By 12 Comments
Arjen posted a good note about MyISAM concurrent-insert features, though I should mention concurrent-insert can be cause of scalablity and peformance… and doing INSERT not often than disabling concurrent-insert with –skip-concurrent-insert can improve MyISAM performance. As I said the reason of…
Post: Using MyISAM in production
June 17, 2006 By 36 Comments
… ones. Concurrency. MyISAM uses table locks and has concurrent inserts which can go concurrently with selects. This is sometimes presented as great concurrency for inserts… can happen concurrently to select statements but it has to be one insert at the time. Happily inserts in MyISAM are rather…
Post: Concurrent inserts on MyISAM and the binary log
May 14, 2008 By 7 Comments
… I had an interesting surprise with concurrent inserts into a MyISAM table. The inserts were not happening concurrently with SELECT statements; they were… the middle of it and prevents concurrent inserts. (You can configure the server to permit concurrent inserts even when there are holes…
Post: Should you move from MyISAM to Innodb ?
January 12, 2009 By 59 Comments
… we usually see clustering by primary key, caching data, higher concurrency, background flushes while on the drawbacks side we see significantly… close to memory size), generally slower writes, slower blob handling, concurrency issues, problems dealing with very large number of tables, slow… for you when you’re running MyISAM but instantly break upon upgrading to Innodb. Features The MyISAM features which forbid moving to…
Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1
January 8, 2007 By 117 Comments
…-pool-size=1500M –innodb-log-file-size=100M –innodb-thread-concurrency=8 –max-connections=1500 –table-cache=512 –net_read_timeout…. Run each query for 1, 4, 16, 64, 128, 256 concurrent threads. 3. For each thread perform a warm-up run… LIMIT queries will be fixed before release. MyISAM shows stable result. InnoDB is better than MyISAM by 58% in case with 4…
Post: Concatenating MyISAM files
November 19, 2012 By 5 Comments
… clearly the lack of concurrency on the read part from InnoDB and then the key management for MyISAM. The server has many dozen drives so it was easy to add more concurrency so I kicked off, from a script, insertions into 16 identical MyISAM files for distinct parts…
Post: Moving from MyISAM to Innodb or XtraDB. Basics
November 22, 2010 By 2 Comments
… regression benchmarks in particular in terms of concurrent behavior. You may have hidden dependencies of MyISAM table lock behavior in your applications, also check if your application handled deadlocks well. MyISAM will not produce deadlocks for Innodb you should always see… than other it is very much workload dependent, and again concurrent tests should be important here. Innodb also may result in…
Post: MyISAM Scalability and Innodb, Falcon Benchmarks
October 12, 2007 By 10 Comments
…) unsigned NOT NULL, PRIMARY KEY (`id`), KEY `val` (`val`) ) ENGINE=MyISAM AUTO_INCREMENT=4097 Table t1 contains about 260,000 records… 121 16 138 As you see running 2-4 threads concurrently we get result by 30% worse than with 1 thread… than 2x in peak which happens to be at 4 concurrent threads. So there is still work to do in addition…
Post: Quick comparison of MyISAM, Infobright, and MonetDB
September 29, 2009 By 30 Comments
… data with SQL statements. I wanted to see how fast MyISAM vs. MonetDB would interpret really large INSERT statements, the kind… 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…
