The past 3 years, 11 months I have worked full time on NDB (MySQL Cluster). It’s been awesome. Love the product and people. In the time I’ve been on the Cluster team, we’ve gone from a small group that would easily fit in the (old old) Stockholm office to one that requires large rooms to house us all in. It’s also been all about smart people (you have to be to work on a distributed database).

With MySQL Cluster 6.4 we’re getting in a bunch of features that have been on the “wide adoption” wishlist. With each release of NDB we’ve gained a wedge of applications that can be used with it - and 6.4 is no exception.

One of the biggest things that’s been worked on is multithreaded data nodes. If you check out Jonas‘ recent posts on 500,000 …

On behalf of Sun Microsystems, I would like to offer my sincerest congratulations to President elect Barack Obama. What an extraordinary accomplishment.

I would also like to extend my congratulations to his web team for having chosen MySQL as the platform behind their election web site, BarackObama.com.

Lest many of you get your hopes up, we cannot guarantee the White House to all MySQL users.

Today Sun Software and Systems group is announcing the best open Web infrastructure and services for MySQL deployments. Sun is unveiling five new  solutions -- designed for our enterprise customers using MySQL --  that marry the market-leading, easy-to-use, open source MySQL database, with the performance and scalability of Sun servers and open storage. More at http://www.sun.com/systems/solutions/mysql/

KEY TAKEAWAYS:

    * With Sun Systems for MySQL, customers can improve the performance of MySQL in high-volume environments to grow their business with improved Web services.
    * Sun Systems for MySQL help ease MySQL deployments without significant application re-engineering efforts and by avoiding complex trial-and-error deployment testing.
    * Sun Systems for MySQL …

A quick solution to a common problem: your MySQL server has thousands of connections, some or most are not persistent. Unless you say otherwise, MySQL will check connections hostnames against the system DNS server. While this is generally not a problem with low traffic, when you are dealing with many concurrent connections you are not only wasting cycles with DNS name resolve, you may also overwhelm or alert your DNS server/provider. The solution? Set skip-name-resolve in the my.cnf file and MySQL will run the connections off of their IP address instead of the DNS name that it resolves to.  

The soft registration deadline for OpenSQL Camp 2008 has passed now; you can still attend, but you won’t be counted into meals and t-shirts. Meanwhile, we have 90 registered attendees, and a truly impressive set of sessions from heavy hitters in the database world. This conference is turning into the event I always [...]

You are just getting started with MySQL on OpenSolaris. You've installed the OpenSolaris Community Edition and CoolStack MySQL. To explore this new environment you decide to run some tests using the sysbench benchmark. After running a number of tests you realize that for some reason the options you are setting in /etc/my.cnf are not getting used.

What is going on? Not to worry, you've just hit a problem common to new users of MySQL on OpenSolaris.

Run this command:

 # /opt/coolstack/mysql/bin/mysqladmin | more

page down until you see:

Default options are read from the following files in the given order:
/etc/my.cnf /etc/mysql/my.cnf /opt/coolstack/mysql/etc/my.cnf ~/.my.cnf

This shows …

Introduction to the Innodb IO subsystem

Basics When a client connects to MySQL, it creates a thread to handle it. This thread executes SQL queries and interacts with the storage engine (for simplicity, lets call them user threads). Innodb uses a four (4) additional threads to implement asynchronous io1. Although Innodb has an option innodb_file_io_threads to control the number of IO handler threads, it has no effect on how many IO handler threads are actually created. These IO handler threads wait and process events in a loop. Each IO handler thread processes different kinds of events. (Insert buffer writes, log writes, datafile writes, and read-ahead or prefetch) Let us now see how different types of IO are handled by Innodb.

Reads Using a simple sysbench read-only test, we notice that all user threads issue reads (pread(2)) to the data files. We can …

Introduction to the Innodb IO subsystem

Basics When a client connects to MySQL, it creates a thread to handle it. This thread executes SQL queries and interacts with the storage engine (for simplicity, lets call them user threads). Innodb uses a four (4) additional threads to implement asynchronous io1. Although Innodb has an option innodb_file_io_threads to control the number of IO handler threads, it has no effect on how many IO handler threads are actually created. These IO handler threads wait and process events in a loop. Each IO handler thread processes different kinds of events. (Insert buffer writes, log writes, datafile writes, and read-ahead or prefetch) Let us now see how different types of IO are handled by Innodb.

Reads Using a simple sysbench read-only test, we notice that all user threads issue reads (pread(2)) to the data files. We can …

Understanding and programming MySQL data load into the DataGridView control is a must for Windows Application Developers today. Many times, in real production environment the end-users need to see a result set of data to make daily business decisions. The main question is about how many records they need to see when the control gets loaded. The answer of the question is defined by the client's business rules. At this point application performance is a critical issue for Application Developers. In this paper I'll show you how load MySQL data into the DataGridView control using VB.NET bound and unbound programming modes. A timer class named Stopwatch for VB.NET will be used to measure the execution time between theses two programming modes.

We're building a MySQL 5.0.67 with OurDelta d7 patchset. This includes some mysql bugfixes, patch fixes (reserved words and backward compatibility) and a few new (and IMHO very interesting) patches. You may have seen a lot of bug/issue/feature completion on launchpad earlier today. The release post will contain full change info.

After successful testruns, we're now just tweaking the scripts responsible for the new build process, so everything is automated and repeatable. Peter Lieverdink is once again doing great work in Debian and bash scripting land.
To have a clean result, we'll restart on all platforms at the end of the tweaking - since all builds feed off the same patched tarball now. Won't take too long. This release will also include a proper source package for each distro, making things much easier for those wanting to indulge with the sources ;-)

…