May 24, 2012

Post: Troubleshooting MySQL Memory Usage

… use reasonable global buffers, such as innodb_buffer_size, key_buffer_size etc, you have reasonable amount …while true do date >> ps.log ps aux | grep mysqld >> ps.log sleep 60 done Check for … intrusive. Run SHOW ENGINE INNODB STATUS and look for memory information block, which can use like this: …

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: 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 – …

Post: InnoDB memory usage

InnoDB uses: innodb_buffer_pool innodb_additional_mem_pool_size innodb_log_buffer_size adaptive index hash, size= innodb_buffer_pool / 64 system dictionary hash, size = 6 * innodb_buffer_pool_size

Comment: MySQL 5.5.8 and Percona Server: being adaptive

….. * Then with a REDO log block size it’s a good point – 4K is the most optimal I/O size for SSD! – however, I have a doubt it makes a huge difference while innodb_flush_log_at_trx_commit=2 is used.. So, to prove it you should present XtraDB results comparing innodb_log_block_size=4096…

Post: Percona Server vs MySQL on Intel 320 SSD

… better experience on SSD is : innodb_flush_neighbor_pages = 0 innodb_adaptive_flushing_method = keep_average innodb_log_block_size = 4096 innodb_log_file_size = 4G Versions: MySQL 5… throughput in Percona Server: increase innodb_log_file_size. There are stability timeline for Percona Server with innodb_log_file_size=8GB And to aggregate results…