Rick James wrote:
> Don't forget that rsync has to read the entire set of files on both the
> source and destination. This is to build a list of chunks to send.
> Then it grabs the chunks, compresses them and sends them, with
> instructions on how to reconstruct.
>
> Unless you are doing an ALTER TABLE or UPDATE on all rows, it would
> swamp the system with modified blocks.
>
That's theoretically a problem. It's basically a trade between CPU and
random disk access and network bandwidth transfering fewer files
In my limited experience (I only have small databases under 1GB and
network speeds of only 100Mbit) it's a good trade (by a LOT). YMMV
Good luck
EdW
| Thread |
|---|
| • One master, two slaves, one of them broken (v 4.0.x) | Edson Noboru Yamada | 22 Apr 2008 |
| • Re: One master, two slaves, one of them broken (v 4.0.x) | Srini | 23 Apr 2008 |
| • RE: One master, two slaves, one of them broken (v 4.0.x) | Rick James | 23 Apr 2008 |
| • Re: One master, two slaves, one of them broken (v 4.0.x) | Edson Noboru Yamada | 23 Apr 2008 |
| • Re: One master, two slaves, one of them broken (v 4.0.x) | Ed W | 5 May 2008 |
| • RE: One master, two slaves, one of them broken (v 4.0.x) | Rick James | 5 May 2008 |
| • Re: One master, two slaves, one of them broken (v 4.0.x) | Ed W | 5 May 2008 |
| • RE: One master, two slaves, one of them broken (v 4.0.x) | Rick James | 5 May 2008 |
| • Re: One master, two slaves, one of them broken (v 4.0.x) | Ed W | 5 May 2008 |