XtraDB storage engine release 1.0.2-3 (Spring edition) codename Sapporo

Today we announce release 1.0.2-3 of our XtraDB storage engine.

Here is a list of enhancements:

  • Move to MySQL 5.1.31
  • Scalability fix — ability to use several rollback segments
  • Increasing the number of rseg may be helpful for CPU scale of write-intentional workloads. See benchmark results.

  • Scalability fix — replaced page_hash mutex to page_hash read-write lock. See benchmark results.
  • Fix broken group commit in InnoDB
  • As you know, the group commit of InnoDB doesn’t work after MySQL 5.0 with binlog.
    We pretend to fix this and added “innodb_enable_unsafe_group_commit=[0|1]” parameter. Note if you set this parameter to “1” record order of binlog and InnoDB transaction log could be not same. But because InnoDB manages transactions in correct order most users may not have problem with this.

  • New parameters in the XtraDB io patches:
    • innodb_ibuf_max_size — Restrict innodb-insert-buffer size
    • innodb_ibuf_active_contract — Enabling it makes the each user threads positive to contract the insert buffer as possible in asynchronous
    • innodb_ibuf_accel_rate — This parameter is additional tuning the amount of insert buffer processing by background thread.
    • innodb_flush_neighbor_pages — When you use the storage which don’t have “head seek latency” (e.g. SSD or enough Write-Buffered), 0 may show better performance.
  • Changed parameter for control read ahead activity. Now it accepts string values:
    • innodb_read_ahead = [none|random|linear|both]
  • Deb builds for Ubuntu

Percona XtraDB 1.0.2-3 (Sapporo) available in source and several binary packages.

XtraDB is compatible with existing InnoDB tables (unless you used innodb_extra_undoslots) and we are going to keep compatibility in further releases. We are open for features requests for new engine and ready to accept community patches. You can monitor Percona’s current tasks and further plans on the Percona XtraDB Launchpad project. You can also request features and report bugs there. Also we have setup two maillists for General discussions and for Development related questions.

Share this post

Comments (10)

  • Sander

    Will the .deb packages work on debian stable? (Lenny?)

    March 3, 2009 at 1:40 am
  • Moritz

    Where are the differences between the rhel5 and rhel5-relay-patch rpms?

    March 3, 2009 at 2:13 am
  • Farid

    Hi, are you planning to import your patches from the 5.0 highperf builds on your last XtraDB-embedded MySQL builds ?

    It would be great to have features like mirror_binlog back.

    Thanks for your great work.

    March 3, 2009 at 8:44 am
  • Vadim


    I have no idea, we have only Ubuntu on board. You can try and report us.

    March 5, 2009 at 10:21 am
  • Vadim


    rhel5-relay-patch is experimental and contains patch overwrite-relay-info, I wrote about it there http://www.mysqlperformanceblog.com/2009/03/04/making-replication-a-bit-more-reliable/

    March 5, 2009 at 10:22 am
  • Vadim


    Yes, we have plans to port all patches from 5.0 to 5.1, we do it as time permits or if someone pays for that.

    March 5, 2009 at 10:23 am
  • Sander


    It seems to work!

    March 9, 2009 at 6:53 am
  • Michael Myles

    Are there any plans for a Windows version. I’m running Server 2008 x64 and it would be really nice to have the xtra features.

    March 31, 2009 at 7:25 am
  • Evgeniy Stepchenko


    Currently we do not plan to support Windows version, sorry.

    April 8, 2009 at 4:39 am
  • yangming

    Innodb on windows are also only use one table space,what a pity!

    April 23, 2009 at 2:38 am

Comments are closed.

Use Percona's Technical Forum to ask any follow-up questions on this blog topic.