Hello Van, > One question regarding this-- you specifically mention this is the case > for MySQL 5.0. Is it also the case for 5.1 or is the situation > different for 5.1? I remember seeing some mention in the 5.1 release > notes regarding performance and replication. > It is different for 5.1 in that this version introduces row-based binary logging, in addition to the statement-based binary logging that is used for replication in earlier versions. This allows the master to log only the changed data rows, which makes it easier on the slave to apply (no need to parse, optimize, execute a statement). This is a good thing in terms of reducing impacts on the slave, but there are naturally trade-offs. If you have simple queries that update many rows, the binary logs will be much larger (affecting disk and network resources). A simple query like "UPDATE huge_table SET col_a = 1" doesn't take up much space in a statement-based binary log, but recording all the data values of all the rows changed could be significant in row-based binary logging.
The best of both worlds is theoretically the "mixed" mode of binary logging, but there's no automatic switching between statement and row-based binary logging based on efficiency, and it's pretty cumbersome to code manual switches into an application to really tune this well. Best regards, Todd Farmer ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Mifos-users mailing list Mifos-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-users
