I’m speaking at the User Conference this year, with a half-day tutorial and three further sessions. The running theme is performance, both in terms of the performance of your queries, and in terms of scaling up.

Scale Up, Scale Out, and High Availability: Solutions and Combinations

This is the big tutorial. It’s difficult to resolve what I’ll be talking about into a few sentences, but think about all of the different technologies available here - replication, partitions, sharding, DRBD, memcached - I’ll be talking about all of them, and more importantly combinations of the different solutions and where the potential performance gains and pitfalls are. I’ll also be using the opportunity to demonstrate some of the more obscure combinations that you can use to provide the environment you need.

…

DTrace has been something that I’ve been trying to get into the MySQL server for more than a year now.

After a combination of my own patches and working with Mikael Ronstrom and Alexey Kopytov we finally have a suite of probes in MySQL 6.0.8. Better still, after a short hiatus while I was busy working on a million-and-one other things, the documentation for those probes is now available: Tracing mysqld with DTrace.

The documentation is comparatively light and deep all at the same time. It’s lightweight from the perspective that I’ve added very little detail on the mechanics of DTrace itself, since there is no need to replicate the excellent guides that Sun already provide on the topic. At the same time, I’ve tried to provide at least one (and sometimes two) D script examples for each of the groups of probes in the 6.0.8 release.

All change at Sun. A new CEO at Zend. Ingres enjoys revenue up 32%. Purple Labs raises funding. Is open source a danger to Microsoft or will Danger bring open source to Microsoft? (Not) open source food. And more.

It’s a good week for business card printers
There was a rush of new appointment and departure announcements this week. As already noted today, Sun has confirmed the departure of Marten Mickos as Sun is combining its Software Infrastructure organization with its Database Group to form a unified open source product group under the leadership of Karen Tegan Padir, vice president of MySQL & Software Infrastructure.

Earlier in the week Monty Widenius confirmed that he has left Sun, along …

I just got news that Marten Mickos, former MySQL CEO, is to depart Sun amid a reorganisation of its infrastructure and database business units. Don’t expect an announcement from Sun on this, but the news is confirmed.

It seems that Sun is combining its Software Infrastructure organization with its Database Group to form a unified open source product group under the leadership of Karen Tegan Padir, vice president of MySQL & Software Infrastructure.

Marten will be transitioning out of Sun by the end of the company’s (current) third quarter.

Marten’s departure is a big loss for Sun and follows quickly after the departures of Monty Widenius and …

There are some basic, golden rules when it comes to having a vibrant community of contributors.

The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.

Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having contributed to the ideas and practices behind these rules.

A) …

There are some basic, golden rules when it comes to having a vibrant community of contributors.

The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.

Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having contributed to the ideas and practices behind these rules.

A) …

There are some basic, golden rules when it comes to having a vibrant community of contributors.

The following are rules I have extracted and learned based on my experience managing and working with engineers actively involved and participating in the Apache/Derby, PostgreSQL and MySQL open-source communities. These rules are also based on extensive discussions with many folks involved with the MySQL community, with the PostgreSQL community and with the Apache/Derby (Java DB) community, over many years.

Before I go through these rules, I would like to thank Marten Mickos for having suggested some of the headings for these rules. (I originally had much longer headings for all of them.) I would also like to thank many of MySQL, PostgreSQL and Java DB colleagues, as well as to many other colleagues involved in open-source development, for having contributed to the ideas and practices behind these rules.

A) …

I received an email from Tarus Balog, CEO of OpenNMS Group, on Friday, taking issue with the language I had used to describe two open source vendors (and I use that term deliberately).

Essentially Tarus objected to me using the term “open source vendor” to describe two companies with Open Core licensing strategies. His email raises a valid point about how we determine which companies are considered “open source vendors” and I wanted to use the opportunity to outline the rules I use to make that decision.

As a technical snafu at our end had prevented Tarus from leaving a comment on the blog I hope he won’t mind me using his words to explain the issue he raised.

He wrote:

“You …