Comments on: Improving InnoDB recovery time

By: Vadim

Vadim — Fri, 17 Jul 2009 04:52:53 +0000

Yasufumi made explanation how it works on this page
http://www.percona.com/docs/wiki/percona-xtradb:patch:innodb_recovery_patches#is_the_buf_flush_insert_sorted_into_flush_list_hack_correct

Your comments are welcome.

By: Apachez

Apachez — Sat, 11 Jul 2009 23:09:27 +0000

Shirish: Im more interrested in why this wasnt fixed by innodb or mysql inc. themselfs all these years?

By: Domas

Domas — Thu, 09 Jul 2009 18:23:20 +0000

I see Mark is getting much better understanding of communities after leaving ‘do no evil’ company

By: Mark Callaghan

Mark Callaghan — Thu, 09 Jul 2009 16:33:53 +0000

…or the community can contribute. I volunteer Domas to document this one.

By: Vadim

Vadim — Thu, 09 Jul 2009 16:15:05 +0000

Ok, ok,

we are preparing explanation. Unfortunately for Yafusumi good explanation in English much harder than writing C code

By: Jay Pipes

Jay Pipes — Thu, 09 Jul 2009 15:47:55 +0000

Agree with Shirish…a comment explaining the change in the code would be very helpful

-jay

By: Gavin Towey

Gavin Towey — Wed, 08 Jul 2009 20:59:52 +0000

Awesome work!

One question though: does this patch affect rollback time as well? Is it related to the crash recovery process?

By: Shirish

Shirish — Wed, 08 Jul 2009 18:08:59 +0000

Amazing. The patch is really tiny, some explanation on how & why this works so beautifully will really help.

By: peter

peter — Wed, 08 Jul 2009 15:42:12 +0000

This is pretty cool !

We should see how recovery math will work now – it may change the log files usable in production dramatically.

By: Domas

Domas — Wed, 08 Jul 2009 06:26:12 +0000

Nice! Last time I looked at the problem, I considered putting the whole structure into RB-tree, which would mean way way more code.
Indeed, explaining some of the changes could be very nice thing to do %)