May 24, 2012

Post: Troubleshooting MySQL Memory Usage

in most cases you do not know where exactly memory is allocated. This was not much of the problem in MySQL 3.23 when there wouldand forgot to remove (or still use for processing). Of course you will see these tables going away if you close connection. In Percona Server you

Post: Aligning IO on a hard disk RAID – the Benchmarks

log_buffer_size = 8M innodb_buffer_pool_size = 128M innodb_log_file_size = 64M innodb_log_files_inand then to Write-Back. 1. Baseline – misalignment on the partition table, no LVM and no alignment settings in the file system. This is what you would

Post: MySQL Slow query log in the table

MySQL 5.1 get MySQL slow query log logged in mysql.slow_log table instead of the file as you had in previous versions. We rarely wouldthe order query come in the log file. If you used to do tail -100 log-slow.log and now change it to SELECT * FROM slow_log

Post: How Percona does a MySQL Performance Audit

the absence of innodb_log_file_size. I won’t give you a full rundown over every option in the file. But again, youthe status values for Created_tmp_tables and Created_disk_tmp_tables, I’ll paste in mysql

Post: Heikki Tuuri answers to Innodb questions, Part II

MySQL would you recommend? I’ve been staying at 4.1.14 because of all thethe first file in the log file group and the SSD dynamic wear leveling algorithm. I’m also wondering if you would recommend using SSD for this purpose, and how

Post: Estimating Replication Capacity

you need to add/remove indexes and do other schema changes you probably would be looking at some methods involving replication if youand log_slave_slow_statements=1 for this method to work. Get the log file which will include all queries MySQL server ran with their times and

Post: The tool I've been waiting for years

log file is being written now and there is a “tail” of pages which just were not removed from thelog file is 50% in cache. Knowing access pattern to the file you can draw some conclusions about how

Post: Evaluating IO subsystem performance for MySQL Needs

you should expect from the system. What I usually look for MySQL is performance in random reads and random writes. Sequential reads and writes are rarely the

Post: Using LVM for MySQL Backup and Replication Setup

you just need to copy files. Fast Recovery Recovery time is as fast as putting data back and standard MySQL crash recovery, andthe backup you will need to restore slaves as well and skip binary logs in your backup process. 7) Unmount filesystem umount /mnt/backup 8) Remove

Post: MySQL Users Conference - Innodb

and uncompression happening in parallel, improving buffer pool usage (currently you may need to both store Compressed and Uncompressed versions of the page in the buffer pool inin MySQL 5.2 or even MySQL 5.1. I surely would like to see it sooner at least in