June 18, 2013

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

… post of a series of articles focused on MySQL 5.6 GTIDs. You can find part one here. Our goal will be to… try! # For s0,s1, s3, s4 mysql> stop slave; mysql> change master to master_port=10002; mysql> start slave; # And then check the… fixed, it is good to be aware of the current limitations.

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

part two in what is now a continuing series on the Star Schema Benchmark. In my previous blog post I compared MySQL 5.5.30 to MySQL 5.6.10, both with default settings using only the…!. MyISAM may be good for raw performance, but there are limitations which MyISAM imposes that are difficult to work with.  MyISAM…

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

… Identifiers are one of the new features regarding replication in MySQL 5.6. They open up a lot of opportunities to make… specific replication topology. However you should keep in mind some limitations of the current implementation. This post is the first one… replication configuration with one master and two slaves, all running MySQL 5.6 with GTIDs disabled. First try: configure only one of…

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

These limitations are part of the reason we decided not to merge MySQL 5.6 global transaction ID into MariaDB. In MariaDB global transaction…

Post: Understanding the maximum number of columns in a MySQL table

MySQL, Percona Server, MariaDB or any other of the MySQL branches/forks, you get to have these odd limitations….(1); } Which is, of course, obvious! Various parts of this limit are: info_length is roughly 2+strlen…TO_BIG_ROW); } Which is curiously gone from MySQL 5.6, it’s replaced by the following …

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

… consistent read view creation. It was originally reported as a part of MySQL bug #49169 and can be described as follows. Whenever… the read-only optimization in MySQL 5.6 to achieve even better scalability while removing the read-only limitations. Let’s take a… read-only) transactions. In this case MySQL 5.6 scalability goes back to the good old MySQL 5.5 times and we see identical results…

Post: The write cache: Swap insanity tome III

…sysctl -p” and we are done. Swappiness solves part of the swapping issue but not all… interleave the allocation of memory for the MySQL process using the numactl utility, drop the…about 28GB and the file upload size limit is 5GB. So, about 28GB was …0 0 138480 1206 19126 16359 3 5 81 12 0 Fri Mar 22 …

Post: 3 ways MySQL uses indexes

… important MySQL limitation – once MySQL runs into the interval range it will not use any further index parts. If you have A BETWEEN 5 AND… A BETWEEN 5 AND 10 range. It is interesting to note this limitation only applies to interval ranges – for enumerated ranges MySQL will use both key parts. Hence if you change…

Post: Flexviews - part 3 - improving query performance using materialized views

… the SELECT portion, adding LIMIT 0 to the SELECT part of the query. convert…. | | 3 | 5337 | 742034 | 3674 | | 4 | 5825 | 738420 | 3593 | | 5 | 5803 | 733495 | 3670 | | 6 | 1579 | 732507 | 3666 | | 7 …from orders: mysql> delete -> from order_lines -> where order_id -> between 1 and 100 -> limit 500;…

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

As the part of analyzing surprising MySQL 5.5 vs MySQL 5.6 performance results I’ve been looking at changes to … | | BASEDIR | /mnt/nfs/dist/5.5.30 | /mnt/nfs/dist/5.6.10 | | BACK_LOG | 50 | 80 | | OPEN_FILES_LIMIT | 1024 | 5000 | | INNODB_AUTOEXTEND…_files_limit was also raised. Unlikely to cause significant gains unless opening and closing files is expensive operation (such as using MySQL