HandlerSocket Benchmark

Introduction

HandlerSocket is a MySQL plugin that talks directly to the storage layer (you can read detailed description here). In this benchmark, I’m going to compare HandlerSocket against MySQL with both CPU-bound and disk-bound workloads.

Configurations

Hardware

• 2 x Xeon E5620 2.40GHz (HT enabled, 8 cores, 16 threads)
• Memory: 4GB
• Disk: RAID-10/2 == 4 × 300GB 15K rpm
• RAID cache: 512MB
• Disk cache: off

Operating System

• RHEL Server 5.4, Linux 2.6.18-164.2.1.el5 x86_64, 64-bit

MySQL

• MySQL Server 5.1.48 with XtraDB
• innodb_buffer_pool_size = 2G
• innodb_flush_log_at_trx_commit = 0
• innodb_flush_method = ALL_O_DIRECT
• Default values for all the HandlerSocket settings

CPU-Bound Benchmark

Workload

• Number of client threads: 100
• Number of requests: 1 million
• Request size: ~30 bytes
• Response size: ~60 bytes
• Read only

Results

Disk-Bound Benchmark

Workload

• Number of client threads: 100
• Number of requests: 10 million
• Record size: 4KB
• 80% read / 20% write

Comments?

Send me email at [email protected] or post your comments here if you have any questions/suggestions.