Threadpool Benchmarks

Here are some benchmarks of some development threadpool code (the ).

The benchmarks were run on three machines:

• facebook-maria1 (Linux, 16 cores)

• pitbull (Linux, 24 cores)

• windows (Windows, 8 cores)

Sysbench 0.4 was used to run some "unit" OLTP tests (point-select and update-nokey), as well as the "classic" OLTP-readonly and OLTP-readwrite. All tests were run with the number of concurrent clients ranging from 16 to 4096, with warm cache, with the sysbench table having 1M records.

The results are quite different on all of the machines tested (the machines are very different, in terms of cores, IO etc), yet threadpool has a positive effect on all 3 machines, and the positive effect seems to grow with the number of cores.

Some notes on how the benchmarks were run:

1. The benchmark client and server used different CPUs - ('taskset' (Linux), or 'start /affinity' (Windows) were used to run the benchmark client on #CPUs/4, the rest of CPUs were used by the server). On the Linux boxes, --thread_pool_size=<N> (where N is number of cores dedicated to the server) was used.

2. innodb_flush_log_at_trx_commit=0 and innodb_flush_method=ALL_O_DIRECT was used to avoid extensive fsyncing, which is ok for the purposes of the testing for this.

OLTP_RO

OLTP_RO facebook-maria1

OLTP_RO pitbull

OLTP_RO Windows

OLTP_RW

OLTP_RW facebook-maria1

OLTP_RW pitbull

OLTP_RW Windows

POINT_SELECT

POINT_SELECT facebook-maria1

POINT_SELECT pitbull

POINT_SELECT Windows

UPDATE_NOKEY

UPDATE_NOKEY facebook-maria1

UPDATE_NOKEY pitbull

UPDATE_NOKEY Windows

_{This page is licensed: CC BY-SA / Gnu FDL}