MariaDB: The 2012 Edition


Published on

MariaDB: The 2012 Edition presented at Percona Live Santa Clara in April 2012.

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

MariaDB: The 2012 Edition

  1. 1. MariaDB: The 2012 Edition Colin Charles, Monty Program Ab colin@montyprogram.com / / @bytebot on Twitter Percona Live Santa Clara, California, USA 11 April 2012
  2. 2. whoami• MariaDB dude at Monty Program Ab• Formerly of MySQL AB/Sun Microsystems• Past lives included FESCO (Fedora Project), | @mariadb
  3. 3. Aims• Two years and four major releases - what is inside MariaDB?• Discuss the broader MySQL ecosystem | @mariadb
  4. 4. MariaDB is currently...• Community Developed• Feature Enhanced • branch of MySQL with more• Backward Compatible • i.e. not a fork | @mariadb
  5. 5. Who’s behind it?• MySQL (database) owned by MySQL AB (company)• Monty Program is just a sponsor of MariaDB• maria-captains: 52% Monty Program, 48% community | @mariadb
  6. 6. When did this begin?• Sun buys MySQL AB in January 2008• Oracle proposes acquisition of Sun Microsystems in April 2009• Widenius decides that beyond the engine (Febuary 2009), focus on MariaDB, a complete database solution | @mariadb
  7. 7. Why MariaDB?• MySQL - an open source product or project?• MariaDB is an open source project | @mariadb
  8. 8. Aims of MariaDB• 100% compatible, drop-in replacement to MySQL• Stable (bug-free) releases• GPLv2 | @mariadb
  9. 9. Compatibility with MySQL• There is no NDB cluster • Tools are similar (some storage engine additional tools for Aria, PBXT)• Client libraries, client- server protocol, SQL • XtraDB enabled by dialect, replication default; InnoDB master-slave all similar included, but not enabled by default• Data files are supported as long as its similar • between versions mariadb-versus-mysql- compatibility | @mariadb
  10. 10. What’s in MariaDB 5.1• Released February 2010 • Croatian collations• Create external • Numerous bug fixes buildsystem using Buildbot + VMs for test • Test cases and coverage +builds improvements• Release filled with • Removal of mutexes storage engines • Compiler warnings gone! • XtraDB, PBXT, FederatedX, (M)Aria | @mariadb
  11. 11. What’s in MariaDB 5.1• XtraDB • http:// (ENGINE=InnoDB) wiki/percona- • enhanced InnoDB xtradb:start designed to better scale on modern hardware; backward compatible, scale better on many cores, use memory more efficiently | @mariadb
  12. 12. What’s in MariaDB 5.1• Extended statistics for slow • PROCESSLIST with query log microsecond precision • based on microslow • TIME_MS in from Percona http:// INFORMATION_SCH EMA.PROCESSLIST slow-query-log- extended-statistics v/time_ms-column-in- information_schemapr ocesslist | @mariadb
  13. 13. What’s in MariaDB 5.1• Table elimination • Pool of threads (MySQL 6 backport - libevent based) • Query highly normalised data, it is • Use a limited set of sometimes possible to threads to handle all resolve a query queries vs one-thread- without accessing some per-connection. Win if tables the query refers most queries are short to e.g. http:// running, and there are few table/row locks. what-is-table- elimination v/pool-of-threads | @mariadb
  14. 14. What’s in MariaDB 5.2• Released November 2010 • en/pam-authentication-• Pluggable authentication plugin • mysql_native_password (20 • User Statistics (userstatsv2) byte) and mysql_old_password (8 • Percona, Google, Weldon byte) included by default Whipple. Understand server activity better, identify • Now with a PAM database loads http:// authentication plugin! statistics • Client, user, index, table statistics | @mariadb
  15. 15. What’s in MariaDB 5.2• Segmented MyISAM keycache • mitigates thread contention for key cache lock, with notable 250% performance improvements http:// v/segmented-key- cache | @mariadb
  16. 16. MariaDB 5.2: SphinxSE• CREATE TABLE t1 (..) • monitor it - SHOW ENGINE=SPHINX ENGINE SPHINX CONNECTION=”sphin STATUS; x://localhost:9312/test”; • can JOIN a SphinxSE• SELECT * from t1 search table and tables WHERE query=‘test using other engines as it;mode=any’; well • matching modes, • limits, filters, ranges v/about-sphinxse supported | @mariadb
  17. 17. MariaDB 5.3: NoSQL• HandlerSocket • Dynamic columns • direct access to • different set of InnoDB/XtraDB “virtual columns” for each row in your • no SQL, simple table CRUD operations on tables • store different attributes for each item (see: e- commerce shops) | @mariadb
  18. 18. MariaDB 5.3: group commit• Group commit in the binary log • note_id=10150261692455933 • sync_binlog=1, innodb_flush_log_at_trx_commit=1 • for-the-binary-log | @mariadb
  19. 19. MariaDB 5.3: replication• Checksums for binlog • mysqldump --single- events (5.6 backport) transaction --master- data => non-blocking• START TRANSACTION backup! (new slave provisioning?) Works WITH CONSISTENT SNAPSHOT works w/ w/XtraDB binlog • row-based replication • obtain binlog pos. w/o for tables w/no primary key blocking other queries | @mariadb
  20. 20. MariaDB 5.3• Progress reporting for • disk access: Index ALTER TABLE/LOAD Condition Pushdown DATA INFILE (ICP), Multi-Range Read (MRR) • join: Classic Hash • mytop included Join, Batched Key Access (ordered• Optimiser changes retrievals via MRR), and many many more • @@optimizer_switc optimizations h flags (default=off) | @mariadb
  21. 21. MariaDB 5.3: Subqueries finally!• DBT-3, 60M line item • optimizer_switch=‘semij rows, 29GB XtraDB oin=on’ / database materialization=on | @mariadb
  22. 22. MariaDB 5.3: Subqueries• Instant EXPLAIN• http:// en/the-query- optimizer | @mariadb
  23. 23. MariaDB 5.3: User Feedback Plugin• New “phone home” plugin (works with Percona server, MySQL)• disabled by default -- please consider enabling it (feedback=on)• feedback_plugin/ | @mariadb
  24. 24. MariaDB 5.3: GIS• MySQL has OpenGIS SFS (Simple feature access, SQL access method)• Now, SQL with geometry types• ST_ prefix• Read more: features-in-533 | @mariadb
  25. 25. MariaDB 5.3: Aria storage engine• Still a crash-safe MyISAM• Has been included and improved upon since MariaDB 5.1• Has group commit in MariaDB 5.2, to speed up multi-user inserts• Is TRANSACTIONAL (crash safe, atomic), but doesn’t do ROLLBACK yet (Aria 2.0) | @mariadb
  26. 26. MariaDB 5.5: a new threadpool• Modified from MariaDB 5.1, great for CPU bound loads, and short running queries• No minimization of concurrent transactions!• Windows (threadpool), Linux (epoll), Solaris (event ports), FreeBSD/ OSX (kevent) More benchmarks: benchmarks | @mariadb
  27. 27. MariaDB 5.5: better for DBAs• Comes with a non- • queries against multiple blocking client library servers? (eg. SHOW STATUS against all • start an operation, do running servers) other work in the same thread, operation • SELECT statements might processed in server, examine too many rows result travels back. and consume many resources. Terminate • multiple queries against execution with LIMIT a single server? (better ROWS EXAMINED utilise more CPUs?) | @mariadb
  28. 28. MariaDB 5.5• MariaDB 5.5 - GA TODAY • release-notes | @mariadb
  29. 29. How do we support all these? Supported LatestVersion Released MySQL till release5.1.42 Feb 2010 Feb 2015 5.1.62 5.1.62 5.2.3 Nov 2010 Nov 2015 5.2.12 5.1.62 5.3.5 Feb 2012 Feb 2017 5.3.6 5.1.625.5.23 Apr 2012 Apr 2017 5.5.23 | @mariadb
  30. 30. How open is MariaDB?• Mailing lists: Launchpad • maria • maria- developers@lists.laun • Bugs database: • https:// • maria- discuss@lists.launchp maria/ • #maria on FreeNode• Code hosting: IRC Launchpad | @mariadb
  31. 31. Worklog• Funding (bounties)• Votes• worklog/ | @mariadb
  32. 32. Knowledgebase• | @mariadb
  33. 33. Deployments, deployments, deployments happy users:, wabtec, Paybox Services, OLX, Jelastic, etc. “We made the switch on Saturday -- and we’re seeing benefits already -- our“MariaDB had these same bugs that we ran into daily optimization time is down fromwith MySQL. However the big difference was that 24 minutes to just 4 minutes” -- Aliwhen we reported these bugs, they were quickly Watters, CEO, travelblog.orgresolved within 48 hours!” -- Dreas van Donselaar,Chief Technology Officer, SpamExpertsB.V. after migrating over 300 servers from MySQL5.0 to MariaDB 5.1. “Migrating from MySQL 5.1 to MariaDB 5.2 was as simple as removing MySQL RPMs and installing the MariaDB packages, then running mysql_upgrade.” - Panayot Belchev, proprietor, Host Bulgaria on providing MariaDB to over 7,000 of their web hosting customers. | @mariadb
  34. 34. Getting MariaDB• is the site + downloads• Get it via OpenSUSE build service• Its in Gentoo, FreeBSD, Homebrew• mariadb• Next up: Debian, Ubuntu (5.5 GA), then Fedora/CentOS | @mariadb
  35. 35. The future?• Merging takes time• Features (different implementations) make it into upstream• Probably moving to JIRA for bugs+worklog functionality | @mariadb
  36. 36. We have a | @mariadb
  37. 37. Support• Monty Program does NRE/engineering work for MySQL/MariaDB (not L1/L2 support)• Support via capable service providers • • SkySQL, Percona, FromDual, Open Query, SoftMethod GmbH | @mariadb
  38. 38. Er.. what about other branches?MySQL Percona MariaDB MySQL Percona MariaDB5.5.20 7.7M 61M 5.5.20 222299 15878435.5.22 16M 60M 5.5.22 438567 1540932 | @mariadb
  39. 39. We’re on social media• facebook:• twitter: @mariadb• google plus: | @mariadb
  40. 40. MariaDB BoF, Ballroom A, 9pm-10pmSalmiakkikossu (black vodka) will be served, Monty will be there, come talk some MariaDB with all!
  41. 41. Q&A? email: colin@montyprogram.com | @bytebot / url: