June 19, 2013

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

innodb_buffer_pool_size=64G innodb_log_file_size=4G innodb_file_per_table innodb_stats_on_metadata=off innodb_file_format=barracuda innodb_log_buffer_size=32M innodb

Post: Benchmarking Percona Server TokuDB vs InnoDB

innodb_flush_method = O_DIRECT innodb_log_buffer_size = 256M innodb_flush_log_at_trx_commit = 1 innodb_buffer_pool_size = 36G innodb_log_file_size = 4G innodb_log_files_in_group = 2 innodb_log_block_size=4096 #####plugin options innodb

Post: MySQL and Percona Server in LinkBench benchmark

… mysqld [.] buf_LRU_free_block(buf_page_t*, unsigned long) | — buf_LRU_free_block(buf_page_t*, unsigned long)…innodb_buffer_pool_size = 30G innodb_flush_method = O_DIRECT innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size=128M innodb

Post: Effect from innodb log block size 4096 bytes

… = 0 innodb_write_io_threads=16 innodb_read_io_threads=16 innodb_io_capacity=2000 I made two runs, one with default innodb-log-block-size ( 512 bytes), and another with –innodb-log-block-size

Post: MySQL 5.5.8 and Percona Server: being adaptive

…:autoextend innodb_file_per_table=1 innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=8M innodb_log_files_in_group=2 innodb_log_file_size=4G innodb_log_block_size=4096 innodb_thread_concurrency=0 innodb_flush…

Post: InnoDB Flushing: Theory and solutions

… The two most important parameters for InnoDB performance are innodb_buffer_pool_size and innodb_log_file_size. InnoDB works with data in memory, …or system failure, InnoDB is logging changes into InnoDB transaction logs. The size of the InnoDB transaction log defines how many changed blocks we can …

Post: Measuring the amount of writes in InnoDB redo logs

… good InnoDB log file size is key to InnoDB write performance. This can be done by measuring the amount of writes in the redo logs… to the log buffer At commit, InnoDB appends those 200 bytes to the same log block and overwrites the same 512-byte file block at offset xxx, then increases Innodb_os_log

Post: Tuning InnoDB Concurrency Tickets

InnoDB. If innodb_concurrency_tickets had been increased to >= 900, then ALL of the PK lookups would be blockedinnodb_flush_log_at_trx_commit = 1 innodb_log_buffer_size = 8M innodb_log_files_in_group=2 innodb_log_file_size=1900M innodb_thread_concurrency=16 innodb_flush_method = O_DIRECT innodb

Post: SHOW INNODB STATUS walk through

…. Innodb can only purge old versions if they there are no running transactions potentially needing them. Old stale uncommitted transactions may block… in log files. By monitoring log sequence number and value up to which logs have been flushed you can check if your innodb_log_buffer_size

Post: Choosing innodb_buffer_pool_size

…10%) larger than your data (total size of Innodb TableSpaces) because it does not only contain …logs, or relay logs, Innodb Transactional Logs also like to be cached otherwise OS will need to do reads to serve writes to these log…give a way to Innodb. Note it is not enough to block OS from swapping – …