# XtraDB5.1.37-7 tuning suggestions?

**URL:** <https://forums.percona.com/t/xtradb5-1-37-7-tuning-suggestions/1266>\
**Category:** Other MySQL® Questions\
**Created:** [September 22, 2009, 8:13pm UTC](https://forums.percona.com/t/xtradb5-1-37-7-tuning-suggestions/1266 "2009-09-22T20:13:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xuekun](https://avatars.discourse-cdn.com/v4/letter/x/b38774/32.png) [@Xuekun](https://forums.percona.com/u/Xuekun)\
**Post date:** [September 22, 2009, 8:13pm UTC](https://forums.percona.com/t/xtradb5-1-37-7-tuning-suggestions/1266/1 "2009-09-22T20:13:09Z")

</div>

Hi, Guys

I compared XtraDB5.1.37-7 and MySQL5.4.1-beta performance using sysbench (simple, read, complex) and dbt2 10WH. All the data can be fully cached into innodb\_buffer\_pool. So no read disk io.

However I found XtraDB5.1.37-7 was 8%~16% lower than mysql5.4.1 for sysbench and dbt2.

Do you have any tuning suggestions?

My hardware is 2 sockets, quad-core processors with HT. OS is RHEL5.2.

Both mysql5.4 and xtradb are started with the below options. Others are the default value.  
–innodb\_buffer\_pool\_size=2300M   
–innodb\_additional\_mem\_pool\_size=20M   
–innodb\_log\_file\_size=650M   
–innodb\_log\_buffer\_size=16M   
–innodb\_lock\_wait\_timeout=50   
–innodb\_flush\_log\_at\_trx\_commit=2   
–innodb\_flush\_method=O\_DIRECT   
–innodb\_log\_files\_in\_group=6   
–innodb\_support\_xa=0   
–innodb\_doublewrite=0   
–innodb-status-file=0   
–innodb\_thread\_concurrency=0 \

Your suggestions/comments are appreciated.

Thx, Xuekun

---

<div class="post-metadata">

**Author:** ![istvan.podor](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/istvan.podor/32/16879_2.png) [@istvan.podor](https://forums.percona.com/u/istvan.podor)\
**Post date:** [December 9, 2009, 6:25am UTC](https://forums.percona.com/t/xtradb5-1-37-7-tuning-suggestions/1266/2 "2009-12-09T06:25:49Z")

</div>

download newer 😉