Introduction When people think about Percona’s microslow patch immediately a question arises how much logging impacts on performance. … innodb_log_file_size=128M innodb_flush_log_at_trx_commit=1 innodb_file_per_table table_cache=2000 Depending on workload different InnoDB… to know how much from performance degradation caused by the microslow patch itself. Let’s do the same tests but logging to…
Comment: Percona Server and Percona XtraBackup
July 16, 2008 By 25 Comments
>5.1.26 >Patches >microslow-5.1.26.patch >innodb_stat-5.1.26.patch >5.1.26.patch where is userstats patch for this version?
Post: Percona RPMS for RedHat 5 / CentOS 5 x86_64
July 31, 2008 By 4 Comments
… slow-log and InnoDB statistics. You can read more here http://www.mysqlperformanceblog.com/2008/04/20/updated-msl-microslow-patch-installation-walk-through/ User / Table / Index statistics (Google’s patch). More here http://www.mysqlperformanceblog…
Comment: Percona builds with patches
August 11, 2008 By 16 Comments
Hi, Olivier, they are compiled against Debian SID 
I am testing the microslow patches with this binaries, but I don’t know the sintax of log_slow_verbosity. I try: set log_slow_verbosity=”microtime,query_plan,innodb“; ERROR 1210 (HY000): Incorrect arguments to log_slow_verbosity Thanks!
Comment: Updated msl (microslow) patch, installation walk-through!
July 31, 2008 By 17 Comments
[...] extended query plan in slow-log and InnoDB statistics. You can read more here http://www.mysqlperformanceblog.com/2008/04/20/updated-msl-microslow-patch-installation-walk-through… [...]
