Created: 2009-06-08
Last modified: 2009-06-08

MySQL Performance: MySQL 5.4 & others @AMD 32cores dbSTRESS

by Dimitri

SSC Team, 2009
Sun Microsystems Inc.

Ces informations sont données à titre indicatif et n'engagent pas Sun Microsystems.

Table of contents

Benchmark Information
Customer Name(s): SSC Team

NDA: no

Contact Information: dimitri (at)

Dates: Juin.2009

Keywords: MySQL 5.4, MySQL 5.Perf builds, XtraDB-5, InnoDB plugin-1.0.3, dbSTRESS, X4600-M2

Hardware Configuration
     - X4600 8CPU AMD Opteron 8384 (quad-core) 2700Mhz, 64GB RAM, 2x FC-port 4Gbit

     - ST6140 2x LUN (500GB RAID1 8HD), each LUN connected by its own fiber channel to the host

Software Configuration
     - Solaris 10 update6
     - UFS

     - MySQL 5.4
     - MySQL 5.Perf builds (4,5,11)
     - XtraDB-5
     - InnoDB plugin-1.0.3
     - dbSTRESS (injector)

Overview: Currently several probe InnoDB code improvements were done by our MySQL Team. I was happy to test them with db_STRESS workloads but on Solaris/SPARC server (M5000). Then discussing with Mikael I was surprised he saw much less improvement from the latest probe builds on his Linux/AMD64 box... And it was unclear why the performance improvement gap is more important on SPARC: due SPARC itself? due Solaris? due a test case?.. To bring more lights and understand better what's going differently on an AMD box I've preferred to avoid to change too many things on the same time :-) So, once one of the latest 32cores AMD server (X4600-M2) was available, I was curious to test it under Solaris10 and connected to the same storage box as M5000 before. And here are my results...

     - test MySQL/InnoDB on AMD box with db_STRESS
     - evaluate a performance gap with some of new builds
     - evaluate an impact of InnoDB thread concurrency
     - etc..

Result(s): see report :-))

Benchmark details
My intention is to replay exactly the same tests as previously on M5000 but on the newest X4600 (8CPU AMD quad core) server. All MySQL configuration files are exactly the same as before too.

Redo log size: I keep the same redo log size = 128MB and the same dirty page percentage = 15% as before even if performance is better with a bigger log size and dirty page percentage will be never considered as I showed before on a such stressful workload. I'll privilege a performance stability during current testing rather seeking for the higher possible numbers..

MySQL versions:

All MySQL versions are :

Benchmark results
Observations :

As usually all full results are presented at the end, but some of them I'd like to present individually.

Full Benchmark Results