… servers, and 384GB for Xeon E5-2600 servers, so sacrificing 10% ram for ZFS metadata is worthwhile.)
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2
… see if you can accommodate with them (think of replication 10 years ago or partioning in 5.1 for instance).
Post: How to fix your PRM cluster when upgrading to RHEL/CentOS 6.4
…@percona3 ~]# clustat Cluster Status for lefred_prm @ Thu May 23 10:20:36 2013 Member Status: Quorate Member Name ID Status…
Post: Choosing a MySQL HA Solution - MySQL Webinar: June 5
… various other flavors of suboptimal. On Wednesday, June 5, at 10 a.m. PDT (1700 UTC), I will be presenting a…
Comment: ZFS on Linux and MySQL
… zfsonlinux (latest) are benchmarked. c) Regarding integrity, XFS from 3.10 is going to have metadata checksums. d) What compression algo…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
You can replicate from MySQL 5.6 to MariaDB 10.0 or vice versa. You just won’t be able …
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
… people wanting to switch from MySQL 5.6 to MariaDB 10.
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
… a mixed replication cluster of MySQL 5.6 and MariaDB 10 using GTID. You will be kept plenty busy trying to…
Comment: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 1
@Kristian Does it mean that MariaDB 10 is incompatible with MySQL 5.6 GTID? You cannot replicate to/from a MySQL 5.6 host using GTIDs?
Comment: How expensive is a WHERE clause in MySQL?
If you use functions on the ‘left hand side’ of a where clause, you ignore any indexes. “and left(a, 10) = ’2008-10-29′” should be “and ’2008-10-29′ = left(a, 10)”

