maria-developers team mailing list archive

Thread
Date

impact of segmented table_open_cache on sysbench results

To: Sergei Petrunia <psergey@xxxxxxxxxxxx>
From: Axel Schwenke <axel@xxxxxxxxxxxx>
Date: Fri, 15 Mar 2013 17:02:05 +0100
Cc: maria-developers@xxxxxxxxxxxxxxxxxxx
Reply-to: axel@xxxxxxxxxxxx
User-agent: Icedove 1.5.0.14eol (X11/20090106)

Hi,

I have been running a sysbench on recent 5.5, 5.6 and 10.0 releases with
tuning a'la Dimitri K. There is one feature that is only in MySQL-5.6.10:
table_open_cache_instances = 16 and I wondered how it would affect the
sysbench result. It makes a *huge* difference.

For the curious I also add the result from a previous run that shows the
impact of tcmalloc vs. glibc malloc.


Disclaimer: hardware is 64 cores (32 w/o HT)


XL

Attachment: oltp_5.6_v3.ods
Description: application/vnd.oasis.opendocument.spreadsheet

Attachment: oltp_5.6_v2.ods
Description: application/vnd.oasis.opendocument.spreadsheet

Follow ups

Re: impact of segmented table_open_cache on sysbench results
From: MARK CALLAGHAN, 2013-03-15