Fri May 23 03:57:45 PDT 2008
- Previous message: [Slony1-general] Slow replication issue
- Next message: [Slony1-general] Slow replication issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hannu Krosing wrote: > My experience is that for high-latency links it is crucial to have the > slon daemon doing the inserts/updates/deletes running on the receiving > side (close to the slave tables) so that the actual data updating > queries do not happen over WAN links. > > You may need to split your replication to 2 separate slony clusters > executed by separate slony daemons to achieve this. Oh, yes, I forgot mentioning, I already run a slon daemon on each server. As for the splitting, wouldn't having the processing done on two servers, and with only two separate data sets (each server being master for one data set) do the same? I noticed that for two data sets originating from different servers, the set with virtually no replication load compared to the other fared pretty well. -- Stephane LAPIE Condapter / WITH EPC / Europe Weathernews, Inc.
- Previous message: [Slony1-general] Slow replication issue
- Next message: [Slony1-general] Slow replication issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list