At Tokutek, Rich Prohaska used Gearman to automate our nightly build and test process for TokuDB for MySQL. Rich is busy working on TokuDB, so I’m writing up an overview of the build and test architecture on his behalf.

Build and Test Process

Rich created a script, nightly.bash, that gets kicked off every night as a cron job. Nightly.bash creates a separate Gearman job for each build target. We have a separate build target (unique binary) for each combination of operating system (e.g. Linux, Windows, etc.) and HW architecture (e.g. i686, x86_64) supported by TokuDB. As we support more operating systems over time, the number of build targets grows quickly so we needed a build and test architecture that scales, and Gearman makes it easy.

Gearman then automatically distributes the build jobs to a set of systems set up as …

At Tokutek, Rich Prohaska used
Gearman to automate our nightly build and
test process for TokuDB for MySQL.  Rich is busy working on TokuDB, so I’m
writing up an overview of the build and test architecture on his behalf.

Build and Test Process

Rich created a script, nightly.bash, that gets kicked off every night as a cron
job.  Nightly.bash creates a separate Gearman job for each build target.
We have a separate build target (unique binary) for each combination of
operating system (e.g. Linux, Windows, etc.) and HW architecture (e.g.
i686, x86_64) supported by TokuDB.  As we support more operating
systems over time, the number of build targets grows quickly so we needed
a build and test architecture that scales, and Gearman makes …

After having reviewed the definition my the previous post (The definitions), the next step is to respond to some questions.

Do you need MySQL High-Availability?

That question is quite obvious but some times, it is skipped. It can also be formulated "What is the downtime cost of the service?". In the cost, you need to include lost revenue from the service and you also need to consider less direct impact like loss of corporate image and other marketing costs. If your downtime cost is under $10/h, you can stop reading this document, you don't need HA. For the others, let's move on!

How to determine which MySQL High-Availability solution is best?

What is really tricky with MySQL is the number of possible HA solutions. From the simplest the most complex let's list the most common …

This is a short post just to make a point on the current performance level of available InnoDB engine implementations. I've made the current testing not in the goal to isolate performance issues, but to see how well the code works now when it meets the business constrain to flush on every transaction!..

The problem is that I've tested recently Oracle 10g with dbSTRESS during several customer's demands and was curious how well MySQL competes now with Oracle :-)) Due Oracle license restrictions I cannot present any Oracle results here (sorry folks, I still need my job :-)) But I've put MySQL into the similar conditions and was curious to see what is the current performance level we may expect on the same platform..

Until now I've always used "innodb_flush_log_at_trx_commit = 2" setting as I expected to isolate internal bottlenecks rather my storage array - but now it'll be "innodb_flush_log_at_trx_commit = 1". Bin log is not used …

Update: Before posting this, I had made an effort to verify that this was not a technical problem. However, Lenz from the MySQL Community team has now replied that indeed Zak Greant's RSS feed had changed it's URL address (see comments), which is why new posts did not appear. So rather than telling anything about Planet MySQL, this post is good evidence of my and others mistrust towards it - thankfully still unfounded. (The roots of this is also discussed in the comments.)

NOTE: Heading of this post was subsequently changed.

Not that I would be surprised of anything anymore, but still.

read more

I’ve had plenty of comments on specific products to Monitoring MySQL Options before providing the completed list. Here are the results from my survey to give everybody a more complete list.

I wanted to provide an update on two things:

• Firstly, we have opened registration for InnoDB/XtraDB training in Los Angeles (Nov 18th).
• The second is that while I am in New York City for training (Oct 29th), I'll be giving a (free) talk at the MySQL Meetup group there (Oct 28th).

We love to speak at Meetup groups.  If you are an organizer feel free to let us know you are interested.  There's no guarantee that we can get schedules to align - but there are a number of Percona consultants that travel regularly.

Entry posted by …

This presentation was be done by Sheeri Cabral of The Pythian Group and went into how to use SHOW ENGINE INNODB STATUS to get more information about your Innodb tables, foreign keys and transactions. This is a great presentation to learn how InnoDB works.

It also went through how to use SHOW ENGINE INNODB STATUS to tune several InnoDB variables:

innodb_adaptive_hash_index
innodb_commit_concurrency
innodb_concurrency_tickets
innodb_file_io_threads
innodb_log_buffer_size
innodb_max_purge_lag
innodb_sync_spin_loops
innodb_thread_concurrency
innodb_thread_sleep_delay

The slides can be downloaded from:

http://technocation.org/files/doc/ShowEngineInnoDBStatus.pdf

(Note that the slides open up to the middle section, which …

How important is page size matter for an IO-bound load? For this note results are limited to a disk-based server. InnoDB uses a 16kb page and you can recompile it to use an 8kb page. After making a few changes to it, I was able to use 4kb pages but I am not sure if that is safe to use in production.

I used sysbench fileio to measure IOPs for different page sizes using an 8-core x86 server with several fast disks. The …

I regret to say, there is no Log Buffer this week, as we’ve all been busy preparing for the Big New Thing coming in a few days. The good news is, we have a Big New Thing coming in a few days. Stay tuned for that, you won’t want to miss it.

LB will be back in a week, with Gerry Narvaja at the helm. In the meantime, I invite you to leave a comment with your favourite DB blogs from this week — MySQL, Oracle, Microsoft SQL Server, DB2, Postgres, Ingres, or other relational/NoSQL databases.