- tl;dr version - slow initial sync with little notification about what's going on QUESTION - Any recommendations on ways to get a little more introspection into the sync process?
- longer version - On iOS. For certain cases, I am forcing the user to sit at a spinning screen on app launch while I do a full sync that's available to them. I need all the data coming down to build some reports and showing an empty screen isn't desirable. I'm watching kCBLReplicationChangeNotification on both the push and pull object for changes. Every time, I seem to get to about 80%, it just hangs for a minute or two. I have tried watching both kCBLDatabaseChangeNotification and kCBLDocumentChangeNotifications. These also seem to stop firing. I am trying to give the users feedback so they don't close the app if it sits for a minute or two just hung. QUESTION - Any recommendations on ways to get a little more introspection into the sync process? My hunch is there may be some issue with sqlite performing batch inserts? (just spit balling). Maybe over the weekend, I can try with the new forestdb and see what performance is like. -j -- 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/CAN8S9iKfAoCr7LF_j3bV-UBbguPba9bQfZt3jQbOH%2Bjaw8siUA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
