June 20, 2013

Post: Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL

… drop in replacement for MySQL, downloads are available  here and from the Percona Software Repositories. Based on MySQL 5.1.69, this release will include all the bug fixes in it. All of Percona’s software is open-source… limiting performance on write-intensive workloads. Bug fixed #1171699. Missing path separator between the directory and file name components in a bitmap file

Post: Percona Server 5.6.11-60.3 first Release Candidate now available

MySQL 5.6.11, including all the bug fixes in it, Percona Server 5…. Server 5.6 series. All of Percona’s software is open-source and…the directory and file name components in a bitmap file name could stop …for the log reads needlessly, potentially limiting performance on write-intensive workloads. Bug …

Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1

…of the new features regarding replication in MySQL 5.6. They open up a lot of opportunities to make…topology. However you should keep in mind some limitations of the current implementation. This post is the…all servers, you can have some slaves using file-based positioning and some other slaves using …

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

…my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default …good for raw performance, but there are limitations which MyISAM imposes that are difficult to …file_format=barracuda innodb_log_buffer_size=32M innodb_buffer_pool_instances=16 metadata_locks_hash_instances=32 table_open

Post: More on MySQL transaction descriptors optimization

MySQL 5.6 virtually eliminates contention on the mutex protecting the list of transactions, its applicability is quite limited…= 52G innodb_log_file_size = 2000M innodb_log_files_in_group = 2 innodb_file_per_table = …_io_capacity = 2000 max_connections=5000 table_open_cache=5000 query_cache_type=OFF …

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

…_LOG_FILE_SIZE | 5242880 | 50331648 | | BASEDIR | /mnt/nfs/dist/5.5.30 | /mnt/nfs/dist/5.6.10 | | BACK_LOG | 50 | 80 | | OPEN_FILES_LIMITopen_files_limit was also raised. Unlikely to cause significant gains unless opening and closing files is expensive operation (such as using MySQL on NFS file

Post: Review of MySQL 5.6 Defaults Changes

… just posted the great summary of defaults changes in MySQL 5.6 compared to MySQL 5.5 In general there are a lot of good… which would mean limit disabled. Very few users actually need DOS prevention this variable strives to provide as MySQL is typically protected by Firewall to begin with. open_files_limit = 5000 strangely enough this is where…

Post: How innodb_open_files affects performance

… there will be a huge waste of space. I used MySQL 5.4.2 for tests which should be as good as… the same, taking 1sec (on the second time) . Whenever innodb_open_files_limit was 64 (virtually all misses ) or 16384 (all hits) performance… with innodb_open_files=16384 I got about same crash recovery speed though with no warnings. So it looks like innodb_open_files_limit=300…

Post: MySQL opening .frm even when table is in table definition cache

MySQL won’t revert to opening the FRM files to read the table definition, but we can see from strace: [pid 19876] openMySQL 5.5 you can find in sql/datadict.cc a function named dd_frm_type(). In MySQL 5… can ignore the upper limit on number of storage engines for MySQL and understanding the …

Post: MySQL 5.6: Improvements in the Nutshell

MySQL University in Raleigh,NC, Tuesday 29th of January I have created the outline of improvements available in MySQL 5…LOCK_open – Support for multiple table_open_cache …) – Faster ORDER BY nidxcol LIMIT N – Persistent Statistics for…Transportable Tablespaces – New configuration files defaults – User …