MySql Replication Questions?

From the look of it, the only benefit you will get from replicating the data is that the master will not need to process the reads, and if you have multiple slaves, the insertion on the slaves should be quicker as well, because the reads are distributed. How much depends on how many reads are being performed in any give time If this will speed up the insertion of the data into the master and slaves significantly then, you may end up with a win As far as locking goes, it doesn't propagate to the slave as far as I know (this is also stated in the faq below). I guess that you could optimise the slaves in rotation, so that only one is out of action at any given time Useful reading dev.mysql.com/doc/refman/5.0/en/replicat....

From the look of it, the only benefit you will get from replicating the data is that the master will not need to process the reads, and if you have multiple slaves, the insertion on the slaves should be quicker as well, because the reads are distributed. How much depends on how many reads are being performed in any give time. If this will speed up the insertion of the data into the master and slaves significantly then, you may end up with a win.As far as locking goes, it doesn't propagate to the slave as far as I know (this is also stated in the faq below).

I guess that you could optimise the slaves in rotation, so that only one is out of action at any given time. Useful reading dev.mysql.com/doc/refman/5.0/en/replicat....

Thanks for your reply Jaydee. I did review the faq (and many other pages) before posting. Having hard time finding specific answers though.

For now, planning on single slave only. So I guess the crux of the question (#1) is if any performance improvement will be seen at all with this configuration? Specifically as it pertains to how the slave executes the writes (replicated over from the master).. – Ben Mar 9 at 18:41 As far as OPTIMZE, it's not clear to me if it is necessary to have these replicated over to the slave (after many updates/deletes..)?

Ideally/preferably, don't want to .. to avoid the slave locking up. – Ben Mar 9 at 18:47 If you only have a single slave I can only imagine a rather modest increase in speed, coming from distributing reads between the two servers. Remember that the slave has to perform all the writes that the master has.As far as OPTIMISE goes, the documentation suggests that you don't have to replicate them at all.

– Jaydee Mar 10 at 20:37 I am thinking of turning off replication on the slave during the high load times on the master (batch jobs running). Then upon completion, direct slave traffic to master (from application layer) and turn replication back on the slave (so it catches up). As far as OPTIMIZE goes, where did you see that you don't have to replicate that?

Can you point me to those docs? Thanks – Ben Mar 14 at 22:28 dev.mysql.Com/doc/refman/5.0/en/optimize-table. Html "By default, OPTIMIZE TABLE statements are written to the binary log so that they will be replicated to replication slaves.

Logging can be suppressed with the optional NO_WRITE_TO_BINLOG keyword or its alias LOCAL." – Jaydee Mar 15 at 9:48.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.