XtraDB/InnoDB CPU bound benchmarks on 24cores server

One of our customers gave me a chance to run some benchmarks on 24-core (intel cpu based) server, and I could not miss it and ran few CPU-bound tasks there.

The goal of benchmarks was investigation of InnoDB-plugin and XtraDB scalability in CPU-bound load.

CPU specification:

I tested MySQL-5.1.30 with InnoDB plugin, Xtradb-1.0.2-1, and XtraDB-1.0.2-2 (rel2). XtraDB-rel2 has not been released yet, we still are doing internal QA for, but it will be ready soon. Main difference XtraDB-rel2 it contains additional scalability fixes for buffer_pool (split_buffer_pool_mutex patch).

my.cnf is

At first I tried sysbench oltp read-only with 10mil rows (the datasize is about 2.5GB), uniform distribution.
The results you can see there: (Results are removed for additional checking)

In the next run I tested sysbench oltp read-write load, and the results are:

Here starting 16 threads the result is dropping down with the same speed as it grew, and with 128 connections we have the same TPS as with 1 connection (and it is on 24-cores box!). XtraDB is slightly better there than InnoDB, but nothing special to be proud of. We definitely we will look how to fix it as next step, read detailed investigation what is the reason of performance drop in next post.

And last one workload I tried is TPCC-like benchmark (you can get it on https://launchpad.net/perconatools), with 100 Warehouses (about 9.5GB datasize).
The result is:

Here the result grows up to 16 connections, but after that InnoDB-plugin is dropping down. XtraDB and XtraDB-rel2 seem quite better, I guess this is mostly because fixes to rw_locks and to buffer_pool mutex (in rel2).

Conclusion: As read-only workload seems fine, read-write cases is something to worry about in 16+ cores boxes.
Intel Based 24 Core Servers are not mainstream these days but as number of cores is increasing now at the same pace as CPU frequency before we believe they are very soon to come. Also in real production there may be not a lot database fits “in-memory” cases – but on other hand 64-128GB RAM per box is not something rare already and recommendation to fit at least active dataset in memory is one we use for our customers.

Share this post

Comments (6)

  • dim Reply

    Hi Vadim,

    did you try to replay the same tests with innodb_thread_concurrency=16 ?


    December 30, 2008 at 6:04 am
  • Vadim Reply


    Nope I did not.
    I know it may fix scalability a bit, but innodb_thread_concurrency=16 on 24-cores box does not make sense.

    December 30, 2008 at 9:57 am
  • peter Reply

    Interesting point though. This is how things degrade with unrestricted concurrency… Often you can get better performance restricting Innodb Thread Concurrency… but our goal is rather fixing internal scaling limits so it is not required.

    December 30, 2008 at 10:36 am
  • Torsten Brumm Reply

    Hi Vadim, did you like to do this test on a 64 Core System with a lot of RAM again 😉 ?

    February 19, 2009 at 5:22 am
  • Vadim Reply


    That would be interesting !

    February 19, 2009 at 11:41 am
  • Torsten Brumm Reply

    pls mail me directly your needs and i will sent you details about login 😉

    Would be interessting to see your results, we only use this box (we have two) for 10% max….never saw a higher load on the box….

    February 20, 2009 at 1:07 am

Leave a Reply