June 19, 2013

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 settings using only the InnoDB storage engine… comments and I promised to follow up with more SSB tests at a later date. I also promised more low concurrency SSB tests… working set fits in memory, InnoDB almost always performs better, at least for this workload. Notes MySQL version used: 5.6.11, custom compiled to

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

MySQL server’s memory usage and you see that it’s starting toto admit that this was probably the most interesting question asked; my initial reaction was, honestly, why would you ever want to use MySQL

Post: Disconnecting a replication slave is easier with MySQL 5.5+ (RESET SLAVE vs. RESET SLAVE ALL)

MySQL 5.5). If you want to know more details, please read on! MySQL 5.0/5.1 First let’s consider MySQLuse CHANGE MASTER TO MASTER_HOST=”: mysql> stop slave; Query OK, 0 rows affected (0.00 sec) mysql> change master to… No [...] Connection settings are …memory. In any case, you will be able to

Post: Galera Flow Control in Percona XtraDB Cluster for MySQL

to allow replication to resume as soon as possible. An example configuration tuning flow control in a master/slave cluster might be: mysql> set…, it keeps reads more up to date without needing to use wsrep_causal_reads….the certification index smaller in memory. It keeps the certification interval …

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

…some of the programs that use it to crash. Fixed by … MySQL replication threads were started before running wsrep recovery, this would lead to memory …tmpdir was specified more than once in the MySQL configuration file (my.cnf… indefinitely when xtrabackup tmpdir was set up on tmpfs. Bug fixed #…

Post: The write cache: Swap insanity tome III

…bad for MySQL performance but it is even more important for HA systems. It is so important to … In summary, you need to interleave the allocation of memory for the MySQL process using the numactl utility, drop …the problem. It happened that the setting vm.dirty_ratio was set to 20 on a 48GB server, …

Post: Is Synchronous Replication right for your app?

… it with by fsyncing to memory (Battery or capacitor-backed…be able to be updated more than just…this: UPDATE achievements SET count = count + 1 where achievement…to a distributed system requires tradeoffs.  Most of us are used to the tradeoffs we take when deploying conventional stand-alone MySQL

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

to the bug #1168032 description for more details. Thanks to Mark McKinstry for reporting the bug and to David Six at Percona Live MySQL… glibc memory allocator is used. Bug fixed …used by the PAM Authentication Plugin couldn’t be loaded with Perl and Python clients when plugin-dir option was set

Post: Virident vCache vs. FlashCache: Part 1

set comparison between vCache and FlashCache and also to conduct some benchmarks for the use case where the MySQL working setto whatever flash memory driver you’ve already had to install, and then further configuration requires modification to…the vCache implementation more useful than the one …

Comment: Virident vCache vs. FlashCache: Part 1

MySQL performance between that card and a traditional SSD – the PCIe card is about 3x faster. By usinguse case, I’m effectively allowing my database to run in memory (not actual RAM, that’s true, but much closer to memory