We are currently using Couchbase 2.1.2 in our Android application.
We have around 70k documents in our app.
We have 5 live queries running in our app.
We know that whenever there will be db change notification, the query runs again, it compares previous results to the new results, and if there is a difference in the result set, it gives a notification.
What’s currently happening is that whenever we are getting frequent changes from our server, the UI thread of the application seems to get blocked. We are not currently passing the optional Executor parameter while adding the QueryChangeListener.
We wanted to confirm that the above process of comparing previous results to the new one, will that take place on the UI thread as well. We looked at the source code and it looks like it uses a SingleThreadScheduledExecutor to compare the previous results to the new one. We wanted to confirm if that was right, and if it is can you please suggest what could be any other process that is blocking the UI thread.