June 20, 2013

Post: Percona Server for MySQL 5.5.31-30.3 now available

… Server has introduced innodb_read_views_memory and innodb_descriptors_memory status variables in the Extended Show Engine InnoDB Status to improve InnoDB memory usage diagnostics. Bugs Fixed: Fix for bug #1131187 introduced a regression that could cause a memory leak…

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

… in this series. Regardless, when the working set fits in memory, InnoDB almost always performs better, at least for this workload. Notes…=justin 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_buffer…

Comment: ZFS on Linux and MySQL

… easy move for a MySQL dba to steal 20GB memory from the Innodb buffer pool to give it to the filesystem. I…

Post: Choosing a MySQL HA Solution - Post-Webinar Q&A

… is brewing. Or if you watch your MySQL server’s memory usage and you see that it’s starting to swap… –skip-grant-tables and insert a few rows into an InnoDB table, but trying to run a simple mysqlslap just hung…

Post: Memory allocators: MySQL performance improvements in Percona Server 5.5.30-30.2

… issue in InnoDB transaction processing that notably affects MySQL performance – for every transaction InnoDB creates a read view and allocates memory for this…) memory allocation for read-view structure is not a direct malloc() call, but rather goes through the InnoDB heap layer – so InnoDB allocates…

Post: The write cache: Swap insanity tome III

… is more complex and swapping can occur because of a memory imbalance between the physical cpus, the sockets and not cores… memory for the MySQL process using the numactl utility, drop the file cache and pre-allocate the innodb buffer pool with the innodb… 10am. Fri Mar 22 10:03:22 UTC 2013 procs ———–memory———- —swap– —–io—- –system– —–cpu—– Fri Mar 22 10:03:22…

Post: Percona Server 5.5.30-30.2 rerelease fixes non-restart issue

… most cases. This significantly improves InnoDB scalability on read-only workloads, especially when the default glibc memory allocator is used. Bug fixed… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the…

Post: Percona Server for MySQL 5.5.30-30.2 now available

… most cases. This significantly improves InnoDB scalability on read-only workloads, especially when the default glibc memory allocator is used. Bug fixed… upstream bug #49169. This also provides much better scalability in InnoDB high-concurrent workloads. Bugs fixed #1131189 (Alexey Kopytov). In the…

Post: Percona XtraDB Cluster 5.5.30-23.7.4 for MySQL now available

…were started before running wsrep recovery, this would lead to memory corruption and server crash. Bug fixed #1132974 (Seppo Jaakola). Conflicting… fixed #1154095 (Alex Yurchenko). If variable innodb_thread_concurrency has been defined to throttle InnoDB access, and work load contained DDL statements…

Post: Virident vCache vs. FlashCache: Part 2

…themselves. When the working set outstrips the available buffer pool memory but still fits into the cache device, vCache shines. … #####fixed innodb options innodb_file_format = barracuda innodb_buffer_pool_size = 4G innodb_file_per_table = true innodb_data_file_path = ibdata1:100M innodb_flush_…