Slack digest for #general - 2019-10-03

[Apache Pulsar Slack <ap...@gmail.com>]

2019-10-02 10:37:14 UTC - Gaetan SNL: @Matteo Merli thank you
----
2019-10-02 18:05:00 UTC - John Koenig: @John Koenig has joined the channel
----
2019-10-02 22:02:51 UTC - BigSam: I wonder if somebody here has ported the C++ or Java client to Android? Is WebSocket the only choice for Android platform?
----
2019-10-02 22:23:11 UTC - John Simmons: @John Simmons has joined the channel
----
2019-10-02 23:21:15 UTC - Ali Ahmed: @BigSam does the java client not work in android ?
----
2019-10-02 23:21:38 UTC - Ali Ahmed: we have java8 compliant so it should just work
----
2019-10-03 01:41:10 UTC - Rajiv Chauhan: @Rajiv Chauhan has joined the channel
----
2019-10-03 03:20:29 UTC - Raman Gupta: Implementing a prototype of a Pulsar work queue consumer with a Shared subscription. I want n threads to be processing simultaneously. Is it idiomatic to create n separate consumers, or create 1 consumer but farm out the work to n threads?
----
2019-10-03 03:26:49 UTC - Matteo Merli: If it’s on the same process, a single consumer with multiple threads calling `receive()` will work well
----
2019-10-03 03:27:25 UTC - Matteo Merli: in most cases, there won’t be much difference between the 2 approaches
----
2019-10-03 03:29:04 UTC - Raman Gupta: Yup, same process. Well, each process with n threads.
----
2019-10-03 03:29:53 UTC - Raman Gupta: Good to know multiple threads can call receive without issues. That should work well, thanks.
----
2019-10-03 03:32:41 UTC - Raman Gupta: @Matteo Merli Just so I'm aware, you say "most cases". Can you explain in which cases there would be a difference?
----
2019-10-03 03:36:28 UTC - Matteo Merli: Well, for example with more consumers, each will have its own prefetch queue. In theory thing could be more parallelized and also there should be no contention while dequeueing messages, leading to a bit higher throughput. In practice, I don’t know what would be the threshold at which the difference would be noticeable.

At the same time, having more consumers will mean that the broker will keep track of each of them.. if you have a lot, at some point it might be more efficient to have more threads on each consumer
+1 : Raman Gupta
----
2019-10-03 03:41:44 UTC - Raman Gupta: As its a work queue with long processing, the slight perf advantage of multiple few consumers is pretty irrelevant for this case. But good to know.
----
2019-10-03 05:29:55 UTC - Sujith Ramanathan: Hi Team,
Can you please acknowledge me the release date of pulsar 2.5.0 ?
----
2019-10-03 05:32:14 UTC - Ali Ahmed: earliest estimate would be 1st week of november
----
2019-10-03 05:45:19 UTC - Sujith Ramanathan: Thanks
----