… InnoDB memory usage diagnostics. Bugs Fixed: Fix for bug #1131187 introduced a regression that could cause a memory leak if query cache was used together with InnoDB. Bug fixed #1170103. Fixed the RPM packaging regression that was introduced with the fix for bug #710799. This regression caused mysql…
Post: MySQL and the SSB - Part 2 - MyISAM vs InnoDB low concurrency
…=/usr/local/mysql socket=/var/lib/mysql/mysql.sock user=justin innodb_buffer_pool_size=64G innodb_log_file_size=4G innodb_file_per_table innodb_stats…=myisam tmpdir=/dev/shm innodb_undo_logs=32 innodb_old_blocks_time=0 table_open_cache=2048 table_definition_cache=16384 innodb_flush_method=O…
Post: ZFS on Linux and MySQL
… ready for the task. Snapshots work best with InnoDB, with MyISAM you’ll have to start the …maybe it is related to better raid controller write cache use. Even the fairly slow gzip-1 mode …ZFS on Linux is a very interesting solution for MySQL backup servers. All backup solutions have an impact …
Post: Is Synchronous Replication right for your app?
… (innodb_flush_log_at_trx_commit != 1), or work around it with by fsyncing to memory (Battery or capacitor-backed write cache… your hotspots were really bad in standalone Innodb, you might consider relaxing the fsync: set innodb_flush_log_at_trx_commit to… to the tradeoffs we take when deploying conventional stand-alone MySQL Innodb with asynchronous slaves. We may not think about the tradeoffs…
Post: MySQL 5.6 - InnoDB Memcached Plugin as a caching layer
… ms max per/cmd 0.0951 ms range per/cmd InnoDB MySQL Select (same table): Fetching [1,000,000] items: 441573 ms… differences: InnoDB store operation was 280% higher (~1.73 ms/op) InnoDB fetch operation was 20% higher (~.06 ms/op) MySQL Select showed 27% increase over InnoDB fetch (~.09 ms/op) This replaced $cache->load…
Post: Benchmarking Percona Server TokuDB vs InnoDB
… datadir=/mnt/data/mysql #for SSD innodb_flush_neighbor_pages = none innodb_adaptive_flushing_method = keep_average innodb_file_per_table = true innodb_data_file… = 4M thread_cache_size = 1000 query_cache_size = 0 query_cache_type = 0 ft_min_word_len = 4 #default_table_type = InnoDB thread_stack…
Post: MySQL and Percona Server in LinkBench benchmark
…_cache_type=0 performance_schema=0 #56only loose-innodb_flush_neighbors=0 loose-metadata_locks_hash_instances=256 innodb_buffer_pool_instances=16 # MySQL 5.5 and 5.6 loose-innodb_io_capacity_max = 15000 #Percona only innodb_adaptive_hash…
Post: The write cache: Swap insanity tome III
… basically controls how important is the file cache for Linux. Basically, with InnoDB, since the file cache is not important we add “vm… for the MySQL process using the numactl utility, drop the file cache and pre-allocate the innodb buffer pool with the innodb_buffer_pool… S3. Why? The push to S3 was especially puzzling since MySQL was not involved. The server was running with nearly 7GB…
Post: More on MySQL transaction descriptors optimization
… true innodb_read_io_threads = 8 innodb_write_io_threads = 8 innodb_io_capacity = 2000 max_connections=5000 table_open_cache=5000 query_cache_… –max-requests=0 –percentile=99 –mysql-user=root –mysql-db=sbtest8t1M –mysql-table-engine=INNODB –mysql-socket=/tmp/mysql.sock –oltp-point-selects=1 –…

