Comments on: On throttling http://dom.as/2009/05/18/crash-recovery-throttling/ Sat, 17 Dec 2011 20:14:59 +0000 hourly 1 http://wordpress.com/ By: Xaprb http://dom.as/2009/05/18/crash-recovery-throttling/#comment-1584 Tue, 19 May 2009 12:58:00 +0000 http://dammit.lt/?p=493#comment-1584 Like basically everything else hard-coded in InnoDB, it needs to be user-configurable. One of these days I’m going to go on a rampage and add about 150 configuration variables for InnoDB.

]]> By: Domas Mituzas http://dom.as/2009/05/18/crash-recovery-throttling/#comment-1583 Tue, 19 May 2009 07:25:32 +0000 http://dammit.lt/?p=493#comment-1583 Antony, there’s nothing really wrong with this kind of throttling, except.. timing.
Make it wait 5ms instead of 500ms, and your I/O system will always have outstanding requests.

Leave it at half a second, and your server will be horrible slacker during crash recovery..

]]> By: Antony Curtis http://dom.as/2009/05/18/crash-recovery-throttling/#comment-1582 Mon, 18 May 2009 22:00:47 +0000 http://dammit.lt/?p=493#comment-1582 That’s cute…. especially considering that most modern hard drives can typically queue 64 IO requests.

Perhaps the developer encountered some OS scalability limit on his development machine?

Or if this is an application feature, a cond var would probably be more suitable.

]]>