Introduction

Evaluating the performance of database systems is a very demanding task. There are a lot of hard choices to be made, e.g.:

• What operating system and operating system version is to be used
• What configuration setup is to be used
• What benchmarks are to be used and how long are the warm-up and measure times
• What test setups are to be used
• What version of the database management system is used
• What storage engine is used

While performance evaluation is mostly machine time, there is still a lot of hard work for the human monitoring the tests. In this blog post we have made following choices:

• We’re using an Intel Xeon E5-2690 @ 2.9GHz CPU containing 32-cores and Linux 3.4.12 with 132G main memory. The database is stored on a Fusion-IO ioDrive2 Duo 2.41TB Firmware v7.2.5, rev 110646, using Driver 3.3.4 build 5833069. The …

There may come a time when you want to collect some of your emails, put them into a database, and search them with Sphinx. If that time has come, you may enjoy this blog post. It will outline one way to get emails from Gmail into MySQL (with PHP’s IMAP extension) so that they become [...]

With an ear to the interwebs, you’ll hear a few things about Docker. Docker is an open platform for developers and sysadmins to build, ship, and run distributed applications. In this blog post, I’m going to outline a very basic example of how to use Sphinx from within a Docker container. What is Docker? This [...]

Introduction

Eventual consistency [1] is a consistency model, which is used in many large distributed databases. Such databases require that all changes to a replicated piece of data eventually reach all affected replicas. Furthermore, the conflict resolution is not handled in these databases, and the responsibility is pushed up to the application authors in the event of conflicting updates. Eventual consistency is a specific form of weak consistency: the storage system guarantees that if no new updates are made to the object, eventually all accesses will return the last updated value [1]. If no failures occur, the maximum size of the inconsistency window can be determined based on the factors such as communication delays, the load on the system, and the number of replicas involved in the replication scheme. We earlier in …

Here are a few videos those of you who are just getting started with Sphinx may find useful. The first video demonstrates a very simple implementation with Ubuntu, PHP, and MySQL. The second video is also about installing on Ubuntu. And, the last video discusses fulltext query syntax. Check ‘em out. Quick Start with Ubuntu [...]

If you would like to see how to set up autocomplete and correction suggestion with Sphinx, PHP, MySQL, and jQuery, take a look at this. This quick video will walk you through the steps of setting up the autocomplete example that we wrote about a while ago. For details on how the whole process works, go [...]

The following sentence is brought to you by IBM Legal. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions.

Okay, now that is out of the way….

If you’re the kind of person who follows the MySQL bugs database closely or subscribes to the MySQL Internals mailing list, you may have worked out that I’ve spent a small amount of time poking at MySQL on modern POWER systems.

Unlike Intel CPUs, POWER CPUs require explicit memory barriers to synchronize memory state between different CPUs. This means that when you’re implementing synchronization primitives, you have one extra thing to get …

Today marks a milestone in terms of the MariaDB project – going forward, the MariaDB project plans to use Github and git for source code management. The migration happens from Launchpad and the bzr tool.

The 10.1 server development (under heavy development now) will happen on Github. You can check it out here: https://github.com/MariaDB/server. Feel free to watch, star or even fork the code, and send us contributions!

Previous maria-captains should now provide their Github IDs so that they can be accorded similar status. Send the IDs to the maria-developers mailing list.

The project eventually wants to move the 10.0, 5.5, 5.3, …

This week we discuss pt-table-checksum for keeping data in sync. Ear Candy is a rational look at why one company chose MySQL; At the Movies is using MySQL in a practical way for Big Data.

pt-table-checksum
pt-table-checksum
pt-table-sync

Episode 151, where we talked about Oracle toolsmysqldbcompare and mysqldiff
Options discussed:
--replicate, --no-create-replicate-table

read more

This week we discuss more Percona tools: pt-online-schema-change and pt-slave-find. Ear Candy is using the CONNECT storage engine to read GPX files, and At the Movies is Performance at Scale with TokuDB.

Events
DB Hangops - every other Wednesay at noon Pacific time

Upcoming MySQL events

OSCon 2014 at the Oregon Convention Center in Portland, Oregon from Sunday July 20th through Thursday July 24th.

Training
SkySQL Trainings

read more