MIkeal's is easy to test: npm install replicate && replicate sourceurl destinationurl
it's probably slower than the current stable release, but more reliable. the new replicator in trunk is apparently the most optimal solution, but it's not released in a stable version yet On Tue, Oct 25, 2011 at 10:57 AM, kowsik <[email protected]> wrote: > Anyone done any benchmarking on @mikeal's replicate vs. the built-in > replicator? For blitz.io, we have east/west continuous replication (on > AWS) and I'm frequently seeing slow-downs and replication stalls (even > during periods of inactivity). Restarting CouchDB will make it quickly > catch up and then things will get backed up again. > > I like the convenience of having the built-in _replicator DB, but > sometimes it takes minutes for docs to get pushed across. We are > running 1.1.0 BTW. > > Thanks, > > K. > --- > http://blitz.io > @pcapr >
