You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2019/05/08 11:57:07 UTC
[GitHub] [couchdb] rnewson edited a comment on issue #2025: _replicate calls
are extremely slow
rnewson edited a comment on issue #2025: _replicate calls are extremely slow
URL: https://github.com/apache/couchdb/issues/2025#issuecomment-490457121
replication is reading the _changes feed, which is ordered (roughly) by last update time, the filter is then applied to the changes as they come through. There might be some internal optimization for the doc_ids filter but given the numbers you're showing, it might not always be possible (or it just might not be that big an optimization).
If you apply the same changes to a document in two separate couchdb servers, you will get the same _rev value and therefore no conflict when you replicate. This is by design. You obviously have to apply the exact same changes in the exact same order to benefit from this, which you might struggle with in practice.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services