June 18, 2013

Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency

MyISAM imposes that are difficult to work with.  MyISAM does not maintain checksum consistency during regular operations and is not ACID compliant. MyISAM and InnoDB

Post: Benchmarking Percona Server TokuDB vs InnoDB

and on data size: InnoDB table: 58GB and 244.980.192 records TokuDB table: 15GB andmyisam_max_extra_sort_file_size = 10G myisam_repair_threads = 1 myisam_recover socket=/var/lib/mysql/mysql.sock user=root skip-grant-tables

Post: Virident vCache vs. FlashCache: Part 2

mysql­-user=root –mysql­-socket=/tmp/mysql.sock ­­–mysql­-table­-engine=innodb ­­\ –oltp­-read­-only=off run The base MySQL configuration (configuration A) appears below: #####fixed innodb options innodbmyisam_sort_buffer_size = 8M myisam_max_sort_file_size = 10G myisam_repair_threads = 1 myisam

Post: Join performance of MyISAM and Innodb

Join speed for MyISAM and Innodb storage engines for CPU bound workload, this is when data size is small enough to fit in memory andand it does not return many rows. I varied the join clause to be id, i and C columns appropriately. CREATE TABLE… there is no need for MySQL to request next row matching…

Post: Innodb Table Locks

joins the table so we observe 2 table instances (note – same table gets counted twice) in use but zero tables are locked. InnodbMyISAM and Innodb when it comes to Table Level Locks. For MyISAM tables running UPDATE query on the table is essentially equivalent to locking table for write (on MySQL

Post: Using CHAR keys for joins, how much is the overhead ?

… are for MySQL 5.1.18 using MyISAM and Innodb tables. This time unlike other benchmarks I decided to do Join not on primary key and have query to read data for both tables

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

MySQL 5.5.30 and MySQL 5.6.10 to the different tables and ran the query: mysql [localhost] {…variable_value,40) var56 from var55 left join var56 on var55.variable_name=…Innodb table but getting MyISAM because Innodb was disabled for some reason was very error prone gotcha. Note this is as far as MySQL

Post: How FLUSH TABLES WITH READ LOCK works with Innodb Tables

…FLUSH TABLES WITH READ LOCK is waiting for that very nasty “full join” …MYISAM like table lock priority problem with pending WRITE query blocks any READ queries to execute on the table. mysqlInnodb tables and you’re not actively changing users, stored procedures etc (which are stored in MyISAM tables

Post: Ultimate MySQL variable and status reference list

innodb_status_fileblogpercona.commanual innodb_strict_modeblogpercona.commanual innodb_support_xablogpercona.commanual innodb_sync_spin_loopsblogpercona.commanual innodb_table_locksblogpercona.commanual innodb_thread_concurrencyblogpercona.commanual innodb

Post: MySQL Server Variables - SQL layer or Storage Engine specific.

Innodb tables in your system does it mean MyISAM variables are not important ? Not really. You still have some tables in MyISAM format in “mysqlInnodb Buffer Pool, Key Buffer etc. It works for certain storage engines which support large pages in general. Currently MyISAM and Innodb