Hi Hideki Itakura, Thank's for such a Wonderfull explanation.
On Friday, October 30, 2015 at 12:47:33 AM UTC+5:30, Hideki Itakura wrote: > > Hi PRASANNA, > > 1) What do you mean about "If downloading tasks remain in the queue" this > point view. > > After starting the pull replication, the pull replicator receives list of > changes (gap between server and local) from Sync Gateway (or CouchDB). The > replicator put changes in queue, and creates tasks to download each > change. Then download tasks will be executed in order. After calling > replicator.stop(), the replicator waits till tasks queue is empty. This is > reason that stop() does not stop replicator immediately. (Note: As I don't > re-read codes, so my explanation might be little different .) > > 2) And any suggestion of when we large database(4000 documents and > all) when looking forward for performance. > > Since v1.1, I believe CBL Java/Android replication performance is good > enough. If each document size is not too big, replicating 4000 documents > could be done in reasonable time. Also the replicator is not using main > thread, so it does not block other stuff. > > Thanks, > Hideki > > > On Wed, Oct 28, 2015 at 11:43 PM, PRASANNA KUMAR <[email protected] > <javascript:>> wrote: > >> @Hideki Itakura and @jens, both you thanks for such nice explanation. >> >> @Hideki Itakura: I have question for you(I would like to know more about >> that part) >> >> >> But other platforms stop is working immediately, I think is that problem >> for only android. And I do not think show replication is stoping after some >> time(When we did stop). >> >> Let me explain small example. I have server database with 250 documents, >> I did start replication and there i've made a one condition if local >> document is more 20 than i'm forcefully stoping that replication. after 3 >> to 5 min i started again than my replication status is showing idle and >> location database document count also 250 than i wonder about that. There >> is one more highlighting point is once i stop the replication conditions >> there if(replication.isRunning) is showing !!false and >> if(replication.getStatus) is showing !!Replication_Active where i have >> little confusion about how process will work(i think, it should be when >> replication is not running than status also should be Replication_Stop). >> And also as you mention that >> Replication.stop() does not stop immediately. If downloading tasks remain >> in the queue, the replicator will stop after processed these tasks. >> >> 1) What do you mean about "If downloading tasks remain in the queue" >> this point view. >> 2) And any suggestion of when we large database(4000 documents and >> all) when looking forward for performance. >> >> I would like to thanks again both of you!! >> >> On Wednesday, October 28, 2015 at 10:32:58 AM UTC+5:30, Hideki Itakura >> wrote: >>> >>> > 1) Is replication creating any thread in backgroup(for start/stop) >>> >>> Yes, Couchbase Lite creates single thread which manages replication. In >>> addition to this thread, Couchbase Lite creates multiple thread for >>> downloading tasks. >>> >>> > 2) And also it taking more CPU resource while doing replication >>> >>> If the replicator needs to process many documents or large documents, it >>> might consume CPU and memory. >>> >>> Thanks, >>> Hideki >>> >>> On Tuesday, October 27, 2015 at 1:10:09 AM UTC-7, PRASANNA KUMAR wrote: >>>> >>>> Ok, Right now i have some log's information what is happing while doing >>>> replication(stop/start) >>>> >>>> 1) When start the replication it is successfully working (but i think >>>> some thing is wrong in showing the counts information i mean >>>> completedChangesCount >>>> and changesCount) >>>> https://friendpaste.com/5pMtcL70U0kprc4blQUIk0 >>>> 2) When i made the stop replication >>>> pullReplication.stop(); >>>> pullReplication = null; >>>> >>>> Here some of log information when i made stop the replication >>>> https://friendpaste.com/5rN7Qrp3S2Xdt2YgEkOO3U >>>> 3) Again i start the replication by the time my location database >>>> showing all documents in location >>>> i mean serverDcouments == localDocuments(true) but replication status is >>>> >>>> 10-27 03:51:16.118 29387-29612/com.edcontrol.edcontrols D/Testing >>>> replicationīš REPLICATION_ACTIVE >>>> >>>> Even not been idle. >>>> >>>> I have few questions about replication part >>>> 1) Is replication creating any thread in backgroup(for start/stop) >>>> 2) And also it taking more CPU resource while doing replication >>>> >>>> How we can solve this problem. >>>> >>>> Thank you >>>> prasanna >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Tuesday, October 27, 2015 at 12:39:41 PM UTC+5:30, PRASANNA KUMAR >>>> wrote: >>>>> >>>>> I think background thread i running in background,once replication is >>>>> start. >>>>> >>>>> >>>>> On Tuesday, October 27, 2015 at 12:02:57 PM UTC+5:30, PRASANNA KUMAR >>>>> wrote: >>>>>> >>>>>> Thank's you reply, Even i did >>>>>> pullReplication.stop(); >>>>>> pullReplication = null; >>>>>> >>>>>> This one also not working >>>>>> >>>>>> On Monday, October 26, 2015 at 6:37:50 PM UTC+5:30, James Nocentini >>>>>> wrote: >>>>>>> >>>>>>> What happens if you dereference the property like this: >>>>>>> >>>>>>> pullReplication.stop(); >>>>>>> pullReplication = nil; >>>>>>> >>>>>>> James >>>>>>> >>>>>>> On Monday, 26 October 2015 13:01:29 UTC, PRASANNA KUMAR wrote: >>>>>>>> >>>>>>>> Hi All, >>>>>>>> >>>>>>>> I have been working couch base lite android one of my project, I'm >>>>>>>> facing the problem while doing PullReplication, I started the >>>>>>>> replication >>>>>>>> but some where i need to stop it(That is my requirement(start/stop)). >>>>>>>> The >>>>>>>> replication started successfully but while stop the replication still >>>>>>>> it is >>>>>>>> running in background. >>>>>>>> >>>>>>>> Note: Here is my code >>>>>>>> >>>>>>>> https://friendpaste.com/1A4v0pXZmHCHz8cSRAINUr >>>>>>>> >>>>>>>> Even if we are stoping but still my replication status always >>>>>>>> showing active state not going to stop state >>>>>>>> >>>>>>>> Can any body me out of here, How i can achieve this or any >>>>>>>> solutions for this problem >>>>>>>> >>>>>>>> Thank's >>>>>>>> prasanna >>>>>>>> >>>>>>>> >>>>>>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Couchbase Mobile" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/mobile-couchbase/ItktPXTY4nA/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/mobile-couchbase/6144930d-1989-47f9-870a-d067b33564a9%40googlegroups.com >> >> <https://groups.google.com/d/msgid/mobile-couchbase/6144930d-1989-47f9-870a-d067b33564a9%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > > Thanks, > Hideki Itakura > Website: http://smilogram.net/ > > -- 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/14bc4147-41c7-4207-95c3-e00a41e301ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
