EmergencyEMERGENCY? Get 24/7 Help Now!

MySQL Binaries Percona build10

 | December 11, 2008 |  Posted In: Percona Software


We made new binaries for MySQL 5.0.67 build 10 which include next fixes:

  • We addressed concerns about potential logging and statistics overhead, so now you can fully turn on / off query statistics for microslow patch and user statistics in runtime.

Next variables were added:

With both slow_query_log = OFF and userstat_running = OFF we have no performance penalties of using of patches.

  • Also we fixed potential memory leaks in microslow and userstats patches, the leak appeared under some workloads.

The -percona release includes:

and -percona-highperf release additionaly includes

You can download RPMs for RedHat / CentOS 4.x and 5.x for x86_64, binaries, sources and patches there

OurDelta builds of this should becoming soon.

Vadim Tkachenko

Vadim Tkachenko co-founded Percona in 2006 and serves as its Chief Technology Officer. Vadim leads Percona Labs, which focuses on technology research and performance evaluations of Percona’s and third-party products. Percona Labs designs no-gimmick tests of hardware, filesystems, storage engines, and databases that surpass the standard performance and functionality scenario benchmarks. Vadim’s expertise in LAMP performance and multi-threaded programming help optimize MySQL and InnoDB internals to take full advantage of modern hardware. Oracle Corporation and its predecessors have incorporated Vadim’s source code patches into the mainstream MySQL and InnoDB products. He also co-authored the book High Performance MySQL: Optimization, Backups, and Replication 3rd Edition.


  • Is there any specific method you suggest to follow upgrade path from 5.0.51 (or whatever) standard mysql to your percona-highperf build?

  • Assuming you’re using RPM with same layout you can upgrade same way as you would upgrade to MySQL versions of them.

    (RPM from RedHat and MySQL for example use a bit different layout for the same platform)

  • Actually just update may not work. As we use different Vendor in RPM .spec the way to install is to delete old RPM (rpm -e) and install new one (rpm -i)

  • kas,

    We have not focused on win32 development, and I even guess some our patches break windows compilation.
    It comes from the fact we fix performance problems on production boxes, but MySQL is rarely run on Win32 production system.

  • I’m going to see if I can set aside some time to do some Win32 builds … And I’ll look at learning how to create msi binaries so that they may be easily installed.

    If I have enough spare moments, I may build the Win32 binaries to permit storage engines to be installed as plugins. The last time I did that was an internal mysql “proof of concept” build I did more than 2 years ago. AFAIK, the zip file is still attached to the worklog. 2

  • Antony,

    We may look into, though I expect problem with compilation (even for Solaris it is not compiled clean). And I don’t think we can make rw_lock working on Win32 (though we may exclude this patch)

  • Hello,
    we have been using the 67-b10 version since around release, and we see a memory usage development that would indicate a meory leak?

    Server version: 5.0.67-percona-highperf-b10-log MySQL Percona High Performance Edition (GPL)


    Week 50 we ran stock redhat mysql . Early week 51 we installed the percona version. since then memory usage has been growing. Last week orso it ran out of swap space, so we added some more today 😉

    We also run https://www.percona.com/mysql/5.0.68/RPM/rhel5/ another place, without the same problems.


Leave a Reply