We prepared RPMs of our release for RedHat 5 / CentOS 5 x86_64 platform.
https://www.percona.com/blog/mysql/RPM/RHEL5/5.0.62/
There was question what patcheset includes and if there is manuals.
We have:
- microsecond resolution in slow-log
- extended query plan in slow-log and InnoDB statistics. You can read more here https://www.percona.com/blog/2008/04/20/updated-msl-microslow-patch-installation-walk-through/
- User / Table / Index statistics (Google’s patch). More here https://www.percona.com/blog/2008/04/24/mysql-extensions-for-hosting/
About the Author
Vadim TkachenkoVadim 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. Vadim’s expertise in LAMP performance and multi-threaded programming help optimize MySQL and InnoDB internals to take full advantage of modern hardware. He also co-authored the book High Performance MySQL: Optimization, Backups, and Replication 3rd Edition.
Great work and thanks for sharing. Rumor has it you use the Information Schema to export the output from the monitoring rather than SHOW {TABLE,USER,INDEX}_STATISTICS. That sounds great. We are still in a MySQL 4.0 mindset and don’t know much about the Information Schema.
We just added support to rotate the slow query log. And we are trying to add SHOW CLIENT_STATISTICS that will aggregate resource consumption by client IP. That should be out in a patch soon.
Hi Vadim,
What is the advantage of using the RHEL5 RPMs vs the generic RPMs on a CentOS/RedHat system?
Thanks
Aaron,
Distribution specific RPMS is better updated for given distributive, as it takes into account standard paths, libraries, config files etc.
But in general generic RPMs also should work.
Mark,
We are not using INFORMATION_SCHEMA yet, but working on this patch right now.