The client is using several threads for the communications. The PublishTask is used to drain incoming notifications from the incoming data buffer independent of the communication threads. But the slowness may very probably originate from the server. Or have you been able to analyse the performance of your client application any more. If the incoming buffer overflows, you will get an onBufferOverflow notification to the SubscriptionNotificationListener, which you can add to the subscriptions. This will be a real indicator that the client side cannot handle data as fast as it is coming in from the server.

Which server are you connecting to?

OK, sounds like your client application doesn’t manage to handle the changes fast enough. What kind of action do you perform in the change handlers yourself? Can you profile the application to find out where the actual bottle neck is?

In practice, it may not be fatal, if the data is handled with a delay, as long as everything is handled. Unless of course you need to react to the changes somehow with a certain response time.

OK, thanks for the note. Good to hear that you found the problem.