… help resolve the obtuse errors that a database sometimes gives related to failures due to constraints. One of the things that…) unsigned NOT NULL AUTO_INCREMENT, PRIMARY KEY (`parent_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 CREATE TABLE `child_A` ( `id` int(10…_1` FOREIGN KEY (`parent_id`) REFERENCES `parent` (`parent_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1 Notice that in the case of child…
Post: ZFS on Linux and MySQL
May 24, 2013 By 17 Comments
… many scripts ready for the task. Snapshots work best with InnoDB, with MyISAM you’ll have to start the snapshot while… compression. I still have to explain this, maybe it is related to better raid controller write cache use. Even the fairly… ray flip a bit on a drive, instead of crashing InnoDB, it will be caught by ZFS and the data will…
Comment: INSERT INTO ... SELECT Performance with Innodb tables.
May 22, 2013 By 22 Comments
… is the related output from show engine innodb status: —TRANSACTION BB0E42A, ACTIVE 3 sec fetching rows, thread declared inside InnoDB 334 mysql tables…
Post: Benchmarking Percona Server TokuDB vs InnoDB
May 7, 2013 By 32 Comments
…_average innodb_file_per_table = true innodb_data_file_path = ibdata1:100M:autoextend innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush… #####plugin options innodb_read_io_threads = 16 innodb_write_io_threads = 4 innodb_io_capacity = 4000 innodb_use_native_aio=0 #not innodb options (fixed…/lib/mysql/mysql.sock user=root skip-grant-tables TokuDB-related options are all defaults, as I understand from documentation TokuDB…
Post: Virident vCache vs. FlashCache: Part 2
May 17, 2013 By 3 Comments
… where a deployment has a massive data set size in relation to both the working set and the cache device size…: #####fixed innodb options innodb_file_format = barracuda innodb_buffer_pool_size = 4G innodb_file_per_table = true innodb_data_file_path = ibdata1:100M innodb_flush_method = O_DIRECT innodb…
Post: MySQL and Percona Server in LinkBench benchmark
May 8, 2013 By 18 Comments
…->mutex: trx0sys.c:196. And most likely this symptom is related to BUG#67808. For MySQL 5.6.11 top mutexes… innodb_log_buffer_size=128M innodb_max_dirty_pages_pct=80 innodb_file_format=barracuda innodb_file_per_table innodb_read_io_threads = 8 innodb_write_io_threads = 8 innodb…
Post: Keynotes, BOFs, and the Community Networking Reception at Percona Live MySQL Conference and Expo
April 15, 2013 By 1 Comment
… are seeing the increasing independence of the ecosystem of MySQL-related products and services from MySQL itself – both in terms of… Engineer, Oracle Topic: “MySQL 5.6: What’s New in InnoDB” Dmitri Kravtchuk, MySQL Performance Architect, Oracle Topic: “MySQL 5.6… 5.6: Redefining Replication” Breakout Sessions on Percona Server and Related Projects Stewart Smith, Director of Server Development, Percona Topic: “Percona…
Post: MySQL 5.6 Compatible Percona Toolkit 2.2 Released
March 25, 2013 By 2 Comments
… are configurable. Also, we removed –lock-wait-timeout which set innodb_lock_wait_timeout because that now conflicts, or is at… received mini overhauls in 2.2 to make their run-related options (–run-time, –interval, –iterations) standard. If you hadn’t… would run once and exit. And each treated their run-related options a little differently. This magic is gone now: both…
Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2
April 15, 2013 By
…, there is another issue in InnoDB transaction processing that notably affects MySQL performance – for every transaction InnoDB creates a read view and… under that mutex. See an example of such an issue. Related bugs: BUG#54982, BUG#49169. 2) memory allocation for read… direct malloc() call, but rather goes through the InnoDB heap layer – so InnoDB allocates heap area and then creates requested block(s…
Comment: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer
April 2, 2013 By 10 Comments
… for two distinctly different modes of operation and use cases. ‘innodb_only’ appears to be handlersocket like, where it’s simply a nosql protocol that accesses existing innodb buffer pool and real time data (good for quick simple… a clear picture why/how you are using these settings related to the use case of your application..
