Yo,

I didn't write most of this code, but most of the new changes are pretty awesome go read about it, grab it, and try it.

We're very careful about getting as much testing as possible before declarnig a new release as stable. Please try it out in your development environments, beat up on it, maybe try it out in staging. Perhaps even be naughty and swap out one production machine with it some late night.

A lot of the changes in this release are good for those high end mysql/etc backed sites where you might be worried about (or are) hitting performance issues with memcached itself. Others like expanded statistics, optional memory optimisations, should be useful for most folks. Please check the release announcements for dustin's more thorough notes :)

A 1.2.7 stable release should …

Yo,

I didn't write most of this code, but most of the new changes are pretty awesome go read about it, grab it, and try it.

We're very careful about getting as much testing as possible before declarnig a new release as stable. Please try it out in your development environments, beat up on it, maybe try it out in staging. Perhaps even be naughty and swap out one production machine with it some late night.

A lot of the changes in this release are good for those high end mysql/etc backed sites where you might be worried about (or are) hitting performance issues with memcached itself. Others like expanded statistics, optional memory optimisations, should be useful for most folks. Please check the release announcements for dustin's more thorough notes :)

A 1.2.7 stable release should …

We introduced Oracle SQL Developer to our developers about a year ago. They seem to like it for querying Oracle, but the MySQL connectivity was quirky in previous releases.Now that Oracle SQL Developer 1.5.4 has been released, I figured I'd give it a try again. I downloaded the software and it started right away with no problem (although I wasn't paying attention and I forgot to migrate over my

We have just released the first binary version of Apache Olio for both the PHP and Rails implementation. Both implementations have been tested quite thoroughly now and we think they are robust enough for serious use - especially for performance testing the workloads.

I introduced Olio in a previous post. It is a toolkit that includes a sample web2.0 application implemented in both PHP and Rails that includes a load generator to drive load against the application.

Please visit the Olio site and download the kits. If you find it interesting, I invite you to come join the project.

While working with Monty Widenius on a bug I reported in MariaDB I was surprised to not get an IRC response for a few minutes. When committed Monty can identify, create a workaround, and patch a problem in code before you have time to read all the responses he also types. See my Monty’s Monument “Passion is a timeless wisdom” comment. One thing I forgot to say in that entry was, while 9pm in New york, it was at last 3am-5am Monty time.

We all love memorable quotes, so here is one.

“sorry, machine died; First time in years”

[9:40pm] montywi: then just try compiling mysqld.o, no need to wait for everything else...
....
[9:58pm] rbradfor: make is clean.
[9:59pm] montywi: sorry, machine died;  First time in years
[10:00pm] rbradfor: laughs …

So a while ago I wrote about fun post about MySQL Scalability to 256 way....

Besides discussion on the thread itself I had a lot of private comments in my mail from Sun/MySQL employees which tended to agree with me on this being the a large stretch.

I would hope Sun/MySQL would tone it down and actually spend time on making things to scale inside MySQL rather than asking you to run tens of MySQL instances to get reasonable performance, but sure enough writing code is harder than writing marketing materials so this work now made it to the Sun blueprint making it recommended reference architecture.

It is also interesting to go back to my old post about …

Nearly every job advertisement for MySQL DBA positions asks for ’shell scripting’, so I decided to investigate what it is. I remembered some performance training, where I was told how forking is bad, and one should attempt to use shell features as much as possible (like, avoid paths to something, what can be used by builtin (e.g. don’t use /usr/bin/[, just pure [ instead )

I tried to automate one MySQL DBA task (reinitializing slave after relay log corruption or after copying in cloned dataset from other server) using just bash - and it kind of worked. From now on I can put 'Shell scripting' proudly on my resume :-)

Next step - learn JCL (some people think this is funny :)

What was your most complicated task solved with shell scripts? :)

#!/bin/bash

HOST=$1
RPASS=$(<passwordfile)

IFS="
" …

ColdStore's performance advantage isn't magic, nor is it a demonstration of a poor MyISAM implementation. It performs better than MyISAM because it maintains the data on disk in a layout that is optimal for the kinds of SELECTs that the ColdLogic analysis applications typically require, bearing in mind how real disks actually perform. It wraps together the effect of MyISAM's INSERT and ALTER TABLE ... ORDER BY, but it is doing it at a granularity that avoids any lock out of SELECTs.

(ALTER TABLE... ORDER BY locks out SELECTs for weeks for a table with just a few hundred million rows).

It performs better than ALTER TABLE...ORDER BY because it reads the disk more "intelligently" for it's specification application and is manages memory for rows itself rather than leaving it to the operating system. (See "Second SELECT" …

ColdStore's performance advantage isn't magic, nor is it a demonstration of a poor MyISAM implementation. It performs better than MyISAM because it maintains the data on disk in a layout that is optimal for the kinds of SELECTs that the ColdLogic analysis applications typically require, bearing in mind how real disks actually perform. It wraps together the effect of MyISAM's INSERT and ALTER TABLE ... ORDER BY, but it is doing it at a granularity that avoids any lock out of SELECTs.

(ALTER TABLE... ORDER BY locks out SELECTs for weeks for a table with just a few hundred million rows).

It performs better than ALTER TABLE...ORDER BY because it reads the disk more "intelligently" for it's specification application and is manages memory for rows itself rather than leaving it to the operating system. (See "Second SELECT" …

ColdStore was produced to solve a particular problem - a performance problem for a particular application. The purpose of making the information available about ColdStore is to find out if there is any interest in any broader use for the solution. If there is interest, we will make it available in an appropriate form.

If you think ColdStore might be of use to you, feel free to contact us. Compare your application requirements with this. Let us know something about what you want to d with it and let's figure out how to go forward.