Comments on: Progress in percents: 0 1 2 3 … http://dom.as/2008/10/26/innodb-crash-recovery/ Sat, 17 Dec 2011 20:14:59 +0000 hourly 1 http://wordpress.com/ By: OurDelta - Builds for MySQL » This week in OurDelta - Vol 2 http://dom.as/2008/10/26/innodb-crash-recovery/#comment-1361 Thu, 06 Nov 2008 00:34:47 +0000 http://dammit.lt/?p=227#comment-1361 [...] the InnoDB recovery code. Surely this can be made faster without a major rewrite. Sure there can be rollbacks also and [...]

]]> By: Peter Zaitsev http://dom.as/2008/10/26/innodb-crash-recovery/#comment-1360 Mon, 27 Oct 2008 07:01:53 +0000 http://dammit.lt/?p=227#comment-1360 Domas,

I wrote about it over a year ago
http://www.mysqlperformanceblog.com/2007/07/17/innodb-recovery-is-large-buffer-pool-always-better/

And there is MySQL bug filed on it http://bugs.mysql.com/bug.php?id=29847 which is of course classified as Feature request.

The workaround one can often use in this case is to REDUCE innodb_buffer_pool_size and remove innodb_flush_method=O_DIRECT so OS cache can be used for caching. This can speed up recovery 10x in some cases.

]]> By: Kevin Burton http://dom.as/2008/10/26/innodb-crash-recovery/#comment-1359 Mon, 27 Oct 2008 06:20:23 +0000 http://dammit.lt/?p=227#comment-1359 Wow… that is REALLY REALLY stupid and NEEDS to be fixed.

It’s also not scalable across cores (obviously) which is why my InnoDB recoveries always use one core.

Dumb dumb dumb.

]]>