Following the launch of the Open Database Alliance some people have assumed that it is only a matter of time before MariaDB becomes the de facto replacement for MySQL.

That assumes that Oracle will allow the development of MySQL to stagnate, either deliberately or through neglect - something that we have expressed our doubts about, but even if that were the case it appears that the GPL (or more to the point MySQL’s dual licensing strategy) may restrict the potential for MariaDB.

Curt Monash recently raised the question of whether closed-source storage engines can be used with MySQL (and, by …

Following on the heels of our memcached performance tests on SunFire X2270 ( Sun's Nehalem-based server) running OpenSolaris, we ran the same tests on the same server but this time on RHEL5. As mentioned in the post presenting the first memcached results, a 10GBE Intel Oplin card was used in order to achieve the high throughput rates possible with these servers. It turned out that using this card on linux involved a bit of work resulting in driver and kernel re-builds.

• With the default ixgbe driver from the RedHat distribution (version 1.3.30-k2 on kernel 2.6.18)), the interface simply hung during the benchmark test.
• This led to downloading the driver from the Intel site (1.3.56.11-2-NAPI) and re-compiling it. This version …

Following on the heels of our memcached performance tests on SunFire X2270 ( Sun's Nehalem-based server) running OpenSolaris, we ran the same tests on the same server but this time on RHEL5. As mentioned in the post presenting the first memcached results, a 10GBE Intel Oplin card was used in order to achieve the high throughput rates possible with these servers. It turned out that using this card on linux involved a bit of work resulting in driver and kernel re-builds.

• With the default ixgbe driver from the RedHat distribution (version 1.3.30-k2 on kernel 2.6.18)), the interface simply hung during the benchmark test.
• This led to downloading the driver from the Intel site (1.3.56.11-2-NAPI) and re-compiling it. This version …

So the CommunityOne conference is coming soon, and earlier this week I finished up the final part of the MySQL/DTrace presentation and preparation so I’m all ready to go.

Want to come along? Get quick access to the Deep Dives:

Online Event Registration – Powered by www.eventbrite.com

Using xtrabackup for copying files can really saturate your disks, and that why we made special option --throttle=rate to limit rate of IO per second. But it really works when you do local copy.
What about stream backup ? Even you copy just to remote box with
innobackupex --stream=tar | ssh remotebox "tar xfi -"
, read may be so intensive so your mysqld feels impact, slave getting behind, etc...

For this there is a nice small utility - pv .

With pv you run:
innobackupex --stream=tar | pv -q -L10m | ssh remotebox "tar xfi -"

and it will limit channel rate to 10 M per second.

Entry posted by Vadim | No comment

Add to: …

I should say I can see results of new engineering/refactoring/bug hunt efforts inside Sun/MySQL.
Over last couple of weeks I started getting a lot of messages from the bugs system about bugs I reported long ago which were deferred to be fixed later or were left in open state. Here is example of such a bug.

I really hope this effort will result in a lot of these old annoyances fixed, which really matches my vision for MySQL - we do not need more big features we need old ones to work well and be convenient.

Entry posted by peter | 5 comments

Add to: …

Replication

===============================================================

1) Before setting up a replication, it could be important to have a clear idea on the why you are setting up a MySQL replication.

The most common one are:
1) Backup purpose
2) Scalability
3) Geographic Distribution
4) High Availability
(More see http://dev.mysql.com/doc/refman/5.1/en/replication-solutions.html)

So stop, relax think and decide which one is yours because it will make the difference.

2) One of the most common question clients asks is HOW the Replication works?

----------------------------------------------------------------------------

There are two main concepts to keep in mind:

1) in MySQL the …

I suppose it looks odd that many of the “6.x” features I’ve blogged about are now “5.4″ features. Sorry about the surprise. In mitigation I observe that this means some things are now scheduled a bit quicker, and some are a lot better than expected. Sometimes it’s hard to know till tests are in.

The current server 5.4 download is here:
http://dev.mysql.com/downloads/mysql/5.4.html.
It does not have all the features yet that we have announced as 5.4.

The features in the current 5.4 download are:

* Scalability, that is, it works faster if you add cores or processors.
A lot of the work for this happened outside the MySQL group per se, it’s lovely to have bunches of performance experts from elsewhere in Sun Microsystems, also known as Sun Classic, doing the tweaks for us. Tests show that 5.4 is faster than any variant, whether genuine MySQL or not.

There’s a …

Today I moved from using Mercurial to using bzr on Launchpad for libmemcached.

Why BZR?

I use Launchpad for pretty much all of my projects at this point. I have been really happy with it, and I have found that bzr works well for Linux/Windows/Mac. Drizzle, Gearman and others are already there so this just simplifies my daily workflow.

This should help with me being able to take patches a bit more quickly (and for that matter do reviews). Having contributors push their patches to their own trees, allows me to easily pull patches and do reviews. With Drizzle we keep a "staging" tree just so that we can regression test any code before it goes to trunk. Since code in Drizzle goes through several people before I see it, we each …

Well, this looks pretty darn interesting. I don't have a lot of time to play with this, but SchemaBank, if it delivers on its promise, looks like a very useful ERD tool at a pretty reasonable price point.

You can export a SQL dump from MySQL or PostgreSQL, import this into SchemaBank, and start going. Or you can start with a fresh schema. You can do visual data modeling, versioning, branching, diffing - in other words, both modeling and change control for your schema.

The UI looks sweet, although I'd be curious how it handles super-large schemas, always the bane of ER tools. It does have "Bird's View" which is a good sign they're thinking in the large.