As you may already know, today Sun announces MySQL 5.4. It's a big step forward and I hope you'll have enough time today to follow all blog posts and other interesting related publications! :-)

I leave my colleagues to tell you what is new in 5.4 and what will come with next releases! (start with Mikael's and Allan's blogs). As well you will not have a whole story if you miss Tim's, Neel's, Richard's, Vince's, David's and many other valuable blogs posts!

From my part I want to present you some "unofficial" dbSTRESS …

There is much excitement today at the launch of MySQL 5.4, so I will relate my story about a project I contributed to this new version.

When we started looking at performance improvements for MySQL, we were interested in "low hanging fruit", or fixes and changes that could reap measurable benefits for users in the short term.

An obvious candidate at that time was the now well-known Google SMP patch. I had seen Mark Callaghan present on this at the MySQL User Conference in 2008, and was interested to investigate.

I was pretty new to InnoDB at that time, and was soon to discover that InnoDB was possibly experiencing poor scalability around its mutexes and read-write locks because InnoDB had a private implementation of adaptive mutexes and …

We have 3 presentations today and you may not have been thinking of attending!  What’s wrong with you.

Oh… did you think I was going to say something else?

Stop by say Hi, seek us out after our sessions and introduce yourself.  I would love for you to stop by  give us your idea’s on Waffle, Bigdbahead, MySQL, benchmarks, Life, Oracle, Baseball, or anything else on your mind.

Today Sun announces MySQL 5.4. This is a great day for customers as they can use systems with many cores much more efficiently. Its a great day for the MySQL community and the MySQL performance team because we made it happen. MySQL 5.4 includes a lot of community contributed fixes as well as many fixes from our team. Mikael and Allan are blogging about all the cool new features and the great scalability of MySQL 5.4. I thought I will take this opportunity to blog about some of the things we tried, and rejected. Sometimes there are a lot of things to be learnt from things that do not work

Early on during our performance investigation, we were trying to see if we can reduce some of the contention in Innodb locks. If you are not familiar with Innodb locks, I suggest you read …

My previous post explored a stored procedure that extended procedure_analyse with the intent of helping DBAs optimize table structure. Here’s an improved version. I’ve followed Arjen Lentz‘s suggestion and added support for the max_elements and max_memory parameters. I also added a new Indexed column to the output, which is an ENUM(‘No’,’Yes’,’Overindexed’). Yes and No are […]

Related posts:

1. Making use of procedure analyse() SELECT Field0[,Field1,Field2,...] FROM TABLE PROCEDURE ANALYSE() is a nice tool...

YARPP powered by AdBistroPowered by

As a final followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on a Sun Fire X4270 platform using the Intel x86 Nehalem chip (2 sockets/8 cores/16 threads). All CPUs were turned on during the runs. The my.cnf was the same as described in the previous blog.

The Sysbench version used was 0.4.12, and the read-only runs were invoked with the following command:

sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \
   --oltp-read-only=on --num-threads=[NO_THREADS] run

The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

Here are the results graphically running on Linux.

The read-only results for MySQL 5.4 show a higher …

As a followup to my MySQL 5.4 Scalability on 64-way CMT Servers blog, I'm posting MySQL 5.4 Sysbench results on the same platform. The tests were carried out using the same basic approach (i.e. turning off entire cores at a time) - see my previous blog for more details.

The Sysbench version used was 0.4.8, and the read-only runs were invoked with the following command:

sysbench --max-time=300 --max-requests=0 --test=oltp --oltp-dist-type=special --oltp-table-size=10000000 \
   --oltp-read-only=on --num-threads=[NO_THREADS] run

The "oltp-read-only=on" parameter was omitted for the read-write tests. The my.cnf file listed in my previous blog was also used unchanged for these tests.

Here is the data presented graphically. Note that the number of vCPUs is the same as the number of active threads up to 64. Active threads beyond …

Today Sun Microsystems announced MySQL 5.4, a release that focuses on performance and scalability. For a long time it's been possible to escape the confines of a single system with MySQL, thanks to scale-out technologies like replication and sharding. But it ought to be possible to scale-up efficiently as well - to fully utilize the CPU resource on a server with a single instance.

MySQL 5.4 takes a stride in that direction. It features a number of performance and scalability fixes, including the justifiably-famous Google SMP patch along with a range of other fixes. And there's plenty more to come in future releases. For specifics about the MySQL 5.4 fixes, check out Mikael Ronstrom's blog.

So how well does MySQL 5.4 scale? To help answer the question I'm going to take a look at some performance data from one of Sun's CMT systems based on the UltraSPARC T2 chip. This …

Yes, we all know that Oracle has acquired Sun. Or intends to. They still have to get through a few hurdles, one of which will be the SEC.

My first thought upon hearing the news (delivered by Sarah, running over to the copy machine yelling, “Did you hear?! Oracle just bought Sun!!” causing me to completely jam the automatic paper feeder, and sending me into personal technology dispair for the rest of the day) was, wow, Oracle just bought MySQL!

Then I read Oracle’s press release:

http://www.oracle.com/us/corporate/press/018363

What? No mention of MySQL. At. All.

Back to the SEC. Acquiring Java, Solaris, and the struggling hardware and services bits of Sun are likely a no-brainer. It’s a verticle acquisition and doesn’t smell very anti-competitive; certainly Oracle’s collective purchase of every major enterprise …

Your intrepid MySQL Cart Team opened the doors thirty minutes early to the Magnolia room and Robert Bochenski was the first one to start an exam this morning. Exams are $25 and we will be letting folks into until 3:00PM. Some come by and take a certification exam.

And at 1PM, I am hosting a 30 minute Certification Q&A session about current exams, future exams, and anything else you want to cover.