This wenesday I’ll be at the MySQL Conference & Expo 2009 as speaker :):

koke and me will show how ANSTE can be used to test the MySQL Cluster.

ANSTE is a testing tool for complex scenarios. It allows to run tests loading some virtual machines, configuring it’s network interfaces and runing some scripts on them.

Kickfire™, Inc. and Sun Microsystems, Inc. today announced a joint MySQL Enterprise™ marketing agreement for the world’s first high-performance MySQL™ data warehousing appliance. The companies will work together to promote the Kickfire MySQL Appliance™ to data warehouse prospects as part of Sun’s MySQL Certified Storage Engine Program.

Virident Systems and Sun Microsystems, Inc. today announced the GreenCloud™ Server for MySQL, a new server which brings ‘in−memory’ computing on an exceptional scale to Sun Microsystems' MySQL™ database. The new server was launched today at the 2009 MySQL Conference & Expo, where Virident is a Diamond Sponsor. Vijay Karamcheti, Virident CTO and Cofounder, will deliver a Keynote Address to the conference on Wednesday at 8:30AM entitled, “Extreme Performance and SmartScaling MySQL with Storage Class Memory Servers”.

While Zack covered the storage engine and appliances sessions pretty well, I feel he’s missed out on a few important new engines (or engine related talks):

• DDEngine will be represented, speaking about Automated data versioning with a storage engine
• Long time MySQL Community Member Beat Vontobel, will be presenting on the SeqEngine, in Solving Common SQL Problems with the SeqEngine
• Kazuho Oku, from Cybozu Labs in Japan, will be talking about Q4M, a queuing engine for MySQL. Mixi.jp uses it for their Twitter like service, so I’d …

Sun Microsystems and Oracle Corporation announced today they have entered into a definitive agreement under which Oracle will acquire Sun common stock for $9.50 per share in cash. The transaction is valued at approximately $7.4 billion, or $5.6 billion net of Sun's cash and debt.

I’ve just successfully configured Drizzle with the PHP Extension and successfully retrieve data to present on a web page.

Qudos to Eric Day for his work. I was able to identify a problem with the current tar release, and a quick confirmation on #drizzle at IRC confirmed a fix had already been commited.

I’m looking forward to evaluating WordPress and Drupal, two popular and common LAMP stack applications that run on MySQL, and to provide any feedback to the community for future support of Drizzle.

I'm in Santa Clara since yesterday, at MySQL Users Conference.

This will be my fifth conference: I missed only one since 2003. I was supposed to come as a guest, but my friend and colleague Dmitri didn't get a US visa, so I am speaking in his stead. Me and Peter Gulutzan will present new all-engine foreign keys. Oh.

So I'm working from Hyatt. It's a great sunny day, the air here is clear and fresh, and everybody is enjoying the weekend.
Well, as mentioned, except me, and maybe Drizzle developers, who already started Drizzle developer conference :)

Musing about this all, I took a step back, and thought: so typical of me:

It's time for the MySQL User Conference now in just a day or so, I have my talks ready, and I been rehearsing them and doing some final editing last week. Except for all the good talks, and meetings with old friends and MySQL expert from inside and outside of Sun, I am also excited to see so many cool things in the Expo.

Most prominent there is the new Storage Engines, like Virident, Kick Fire and InfoBright. Also, we'll see what MySQL has up it's sleves this year (no, I do not know, this will be a surprise for me also). There are many more Storage Engines to look at, including the InnoDB plugin.

A theme here seems to be performance, quite clearly, so we'll …

This is the second part in in the series of posts about scaling Drupal stack. The first part can be found here.

GLB has been fixed to support unlimited connections and now I can benchmark Drupal stack cluster on large EC2 instances. What I'm looking for here mainly is how much Galera synchronization overhead affects performance here. With small instances everything was pretty much clear: single core hindered by Xen was an easy traget, and scalability was predictably linear. Large instance is dual core, and Xen interference is minimal, Galera synchronization and serialization effect must be more pronounced. How desperately bad is it?
We'll start with looking at HTTP load "elasticity" on large EC2 instance:

Users   Throughput      Latency         Errors
        (req/min)       (ms, median)    (%) …