Brian Aker wrote: > Hi! > > On Aug 14, 2008, at 5:27 AM, Baron Schwartz wrote: > >> The problem I'm pointing towards is that currently the synchronization >> between the binlogs and InnoDB causes a lot of extra fsyncs for each >> commit. > > Unfortunately there is only a couple of solutions for a safe commit. > > 1) Let one engine lead the charge on sync (I like this). > 2) Store binlog in Innodb (Hmmm might work). > 3) Punt like we did in the past (I dislike this) > 4) ?
4) Have a 2-phase commit transaction marshaller within the kernel which would be a no-op when only on a single server or a pushdown when only a single storage engine is used. -jay _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
