It would be nice if pre-allocated binlog files were possible, but performance results from ext-3 overstates the benefit to be had. If you care about performance with the binlog enabled then don't use ext-3: http://www.facebook.com/note.php?note_id=194501560932 On Mon, Dec 13, 2010 at 10:08 PM, Sergei Golubchik <serg@askmonty.org> wrote:
Hi, Arjen!
[moving to the public list]
On Dec 14, Arjen Lentz wrote:
Hi all
Can we adopt/implement http://forge.mysql.com/worklog/task.php?id=4925 in MariaDB? The benchmark info is in the item, and looks quite interesting. The author tested it using a separate tool to preallocate the binlog, but it should be straightforward implementing this inside the server, that'd also be much easier to manage without extra fuss for a DBA.
You mean - before it gets into 5.6 and we merge it the normal way? Or you mean - with a different implementation (w/o mysqlbinlogalloc) ?
Regards, Sergei
P.S. These are the changesets:
final version: http://lists.mysql.com/commits/113309 http://lists.mysql.com/commits/113306 http://lists.mysql.com/commits/113307 review comments: http://lists.mysql.com/commits/116965 http://lists.mysql.com/commits/121478
_______________________________________________ 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
-- Mark Callaghan mdcallag@gmail.com