Re: [Maria-developers] what pros/cons of storing binary log in an InnoDB table?

These are some results from sysbench for the GA release of Drizzle, it was about a 10% hit having the transaction log stored in inno. The only automated testing I did was sysbench I do recall how i/o bound sysbench is. https://lists.launchpad.net/drizzle-benchmark/msg09626.html Cheers, --Joe On Mon, Jan 28, 2013 at 8:38 PM, Vadim Tkachenko wrote:

Stewart,

I would pretty much like to see benchmarks numbers, especially under IO-bound workload before agreeing that it performs well.

...

Kristian Nielsen writes:

...

You will be writing your data *6* times: To the real table, when flushing its buffer pool pages. To the double-write buffer while flushing, and to

On Mon, Jan 28, 2013 at 5:05 PM, Stewart Smith wrote: the redo

...

...

log before flushing. Then to the binlog table, and before that to the redo log and the doublewrite buffer. I could never reconcile myself with this.

Mind you, it performs really quite well due to the reduced fsync()s and (at least in Drizzle code) was rather trivial to implement. Big bang for buck :)

-- Stewart Smith

-- Vadim Tkachenko, CTO, Percona Phone +1-925-400-7377, Skype: vadimtk153 Schedule meeting: http://meetme.so/VadimTkachenko

Join us in Santa Clara for the annual Percona Live MySQL Conference & Expo 2013! http://www.percona.com/live/mysql-conference-2013/

Looking for Replication with Data Consistency? Try Percona XtraDB Cluster!

_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : maria-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp