https://bugzilla.wikimedia.org/show_bug.cgi?id=49652
--- Comment #2 from Ori Livneh <[email protected]> --- (In reply to comment #0) > To better match between development and production environments, vagrant could > install the same version of MariaDB used for wikimedia production databases. I support the idea in principle. Do you have a scenario in mind where the difference is likely to be significant? I'd simply like to understand the trade-offs. Even if we use the same binaries as prod, there is a massive difference between a single MySQL instance under single-user load vs. a massive MySQL cluster w/master-slave replication operating under standard Wikimedia load. So all other things being equal, sure, let's use MariaDB, but if it is even slightly more complicated to install and configure, it may not be worth it. (In reply to comment #1) > That's just a Wikimedia thing... Hardly. openSUSE[0], Slackware[1], Arch[2], Fedora[3], RHEL[4], and OpenBSD[5] have replaced Oracle's MySQL with MariaDB as the default. Debian & Ubuntu have been dragging their feet a little, but I bet it won't be very long before they too make the switch. [0]: http://blog.mariadb.org/opensuse-12-3-released-with-mariadb-as-default/ [1]: http://slackware.com/ [2]: https://www.archlinux.org/news/mariadb-replaces-mysql-in-repositories/ [3]: http://www.zdnet.com/oracle-who-fedora-and-opensuse-will-replace-mysql-with-mariadb-7000010640/ [4]: http://www.theregister.co.uk/2013/06/15/red_hat_to_ditch_mysql_for_mariadb_in_rhel_7/ [5]: http://blog.mariadb.org/mariadb-now-in-openbsd-ports-tree/ -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
