Ok. Thanks for the clarification Jens. On Thursday, April 14, 2016 at 2:15:21 PM UTC-6, Jens Alfke wrote: > > > On Apr 14, 2016, at 11:30 AM, Brendan Duddridge <[email protected] > <javascript:>> wrote: > > So I'm wondering if it would be adequate to just display to the user the > CBLDatabase lastSequenceNumber property? At least they could look at one > database and then the other and see, oh, this one is behind that one or, I > can see it's catching up. > > > The sequence numbers in two databases don’t have any relation to each > other, though; if you sync databases A and B, their lastSequenceNumber > values won’t necessarily be the same. Due to implementation details they > may be fairly close if you use SQLite storage, but if you use ForestDB > storage they’re usually going to be very different. Other factors like > filtered replications will throw them off even more. > > The answer to the question in the subject is to let the replication run > till it goes idle or stops, with no errors. > > I wish there were a better answer, but I’ve found that accurate progress > measurement comes at the expense of performance and memory footprint. As > we’ve optimized the replicator we’ve lost accuracy in tracking progress. > > —Jens >
-- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/00ebfaa2-487c-49a4-aff9-4aa20d1ac92c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
