June 20, 2013

Post: How Percona does a MySQL Performance Audit

to change. We also want to know the operating mode you expect us to work in. Maybe you want us tothe way, the slow query logs in the stock MySQL server are extremely limited, and for serious analysis it’s basically mandatory to use a server that has the

Post: Heikki Tuuri answers to Innodb questions, Part II

to be sure. In Innodb besides scalability changes into increase size of your Innodb log files to be able to use a lot of memory for write bufferingmysql processes drops rapidly when you increase the amount of system memory. We just deployed a new Linux/Mysql server

Comment: MySQL Server Memory Usage

mysql/slow-queries.log max_connections=650 open_files_limit=6144 max_connect_errors=10000 interactive_timeout=3600 wait_timeout=3600 key_buffer_sizebuffer_size=8M # Lowered from 32M according to MySQL innodb_additional_mem_pool_size=20M innodb_file_io_threads=4 innodb_lock_wait_timeout=15 # CHANGED

Post: Side load may massively impact your MySQL Performance

to spare. We’re using Percona Server 5.5.15 for this test with buffer pool sizeto non zero value, if not I would strongly suggest changing default from zero in MySQL

Post: Innodb Caching (part 2)

keys, when everything could be kept uncompressed in buffer pool as well as in case of complere disk IO bound workload. It is hard tochanging page size without recompiling the server, though I expect results for 16K and 16K Compressed to be very similar on MySQL

Post: Choosing innodb_buffer_pool_size

MySQL needs – these include MySQL buffers – query cache, key_buffer, mysql threads, temporary tables, per thread sort bufferMySQL in memory by using –memlock – just be careful as in case you have memory usage spike you may have MySQL Server

Post: MySQL Users Conference - Innodb

the average size pages were compressed to for data and for various indexes. How many “fragmented” pages do we have in thein INSERT IGNORE and ON DUPLICATE KEY UPDATE cases. Now In MySQL 5.1+ it is also possible to

Post: Why MySQL could be slow with large tables ?

Buffers, Indexes and Joins. Buffers First thing you need to take into account is the fact – situation when data fits inthe reasons elevating this problem in MySQL is lack of advanced join methods at this point (the work is on a way) – MySQL

Post: Impact of memory allocators on MySQL performance

the control. In this post I’m going to check impact of several memory allocators on the performance/scalability of MySQL server in thebuffer_pool_size=52G For every malloc allocator perform the following steps: start Percona serverhow mysqld footprint is changed during the test cycle and what is the

Post: SHOW INNODB STATUS walk through

how to use this info to improve MySQL Performance. Tokey which failed as well as the closest match which was located in parent table. There is a lot of scary information inbuffer_size is optimal – if you see more than 30% of log buffer size being unflushed you may want to