June 20, 2013

Post: trx descriptors: MySQL performance improvements in Percona Server 5.5.30-30.2

April 12, 2013 By 3 Comments

… relatively small memory block which, …in autocommit. Which is the perfect case for read-only optimization in MySQL 5.6 and as you can see MySQL 5.6 shines in…in the alpha stage. We are going to blog about other MySQL performance improvements introduced in our latest Percona Server release, stay tuned…

Filed Under: Benchmarks, MySQL Tagged With: , , ,

Post: Galera Flow Control in Percona XtraDB Cluster for MySQL

May 2, 2013 By 5 Comments

…soon as possible. An example configuration tuning flow control in a master/slave cluster might be: mysql> set global wsrep_provider_options=”gcs…small fc_limit does however keep the certification index smaller in memory. It keeps the certification interval small, which minimizes replication conflicts…

Filed Under: Insight for DBAs, Percona Live, XtraDB Cluster Tagged With: , , ,

Post: Is Synchronous Replication right for your app?

May 14, 2013 By 18 Comments

… work around it with by fsyncing to memory (Battery or capacitor-backed write cache), …MySQL replication is asynchronous. What about semi-sync MySQL replication? It’s actually much worse than Galera.  As I illustrated in…update much faster.  I see this tuning very frequently for “performance” reasons …

Filed Under: MySQL, Percona Software, XtraDB Cluster Tagged With: , , , , , ,

Post: Virident vCache vs. FlashCache: Part 1

May 16, 2013 By 3 Comments

…some benchmarks for the use case where the MySQL working set is significantly larger than the … requires building a separate kernel module in addition to whatever flash memory driver you’ve already had to …statistics via /proc, I’d vote in the other direction. Stay tuned for part two of this series…

Filed Under: Benchmarks, Hardware and Storage, MySQL Tagged With: , , , , ,

Post: What to tune in MySQL Server after installation

September 29, 2006 By 118 Comments

… to work as MySQL DBAs or be involved with MySQL Performance in some way is to ask them what should be tuned in MySQL Server straight… are where in wild which are running with default settings. Even though you can tune quite a lot of variables in MySQL Servers only… affect performance too much, at least on OS with decent memory allocators. Still you might want to have it 20MB (sometimes…

Filed Under: Insight for DBAs Tagged With:

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

February 21, 2013 By 8 Comments

… are less than 200 tables in this system. innodb_stats_on_metadata is disabled by default in MySQL 5.6 Welcome to much… 4MB instead of 1MB now allowing MySQL to handle larger queries. Makes sense as amount of memory available is much larger these… I guess is one of the component of purging fine tuning in MySQL 5.6 innodb_file_per_table is now ON by…

Filed Under: Insight for DBAs, MySQL Tagged With: , , ,

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

March 21, 2012 By 10 Comments

… execution plan, is not sufficiently tuned and it is recommended to turn…In-memory workload Now let’s see how effective is MRR when the workload fits entirely in memory. For the purpose of benchmarking in-memory…in MySQL 5.6, is that because of a bug in MySQL 5.6 code? As MRR was used in both MySQL…

Filed Under: Benchmarks, Insight for DBAs, MySQL Tagged With: , , , , , , , , , , , , , ,

Post: Should we give a MySQL Query Cache a second chance ?

April 10, 2011 By 64 Comments

… implementation which appeared in MySQL 4.0 Query Cache was designed to work with single core systems and relatively small memory amounts, both… Cache Storage Engines MySQL Query Cache now stores queries in local memory, which is great however memory amount might be limited especially in constrained environments… be done by external script which can have application-specific tunings to prioritize which queries are more important to refresh for…

Filed Under: Insight for DBAs, MySQL

Post: MySQL 5.6.10 Optimizer Limitations: Index Condition Pushdown

March 14, 2013 By 2 Comments

… the same “SELECT one_indexed_column” query in MySQL 5.6.10. This turned into a…in memory). Also, I was testing, as I said before, index condition pushdown. Let’s have a look at the EXPLAIN output: mysql… more manual care and tuning now. MySQL is conservative about “Using index” -in most cases it will…

Filed Under: Events and Announcements, Insight for Developers, MySQL Tagged With: , ,

Post: InnoDB Full-text Search in MySQL 5.6: Part 2, The Queries!

March 4, 2013 By 7 Comments

…text Search in MySQL 5.6: Part 2, The Queries![/caption] This is part 2 in a 3 part series. In …. We are using MySQL 5.5.30 and MySQL 5.6.10 with no configuration tuning other than to …_STOPWORD` ( `value` varchar(18) NOT NULL DEFAULT ” ) ENGINE=MEMORY DEFAULT CHARSET=utf8 The docs tell us that …

Filed Under: Insight for DBAs, Insight for Developers, MySQL Tagged With: , , , , ,
« Older Posts