Hi Andrews and Matteo,
Thanks guys. I’ll treat the issue as a second phase design concern where I can
time out resources associated with unused producers in the client.
Regards,
Dave
> On Nov 1, 2017, at 2:39 PM, Sahaya Andrews wrote:
>
> We have tested 50,000 topics from a client(java) box,
We have tested 50,000 topics from a client(java) box, each topic with
one producer and one consumer. On an average around, 80-100 topics
loaded per second. On the server side, it had 3 brokers and 3 bookies.
Andrews.
On Wed, Nov 1, 2017 at 1:28 PM, Dave Fisher wrote:
> Hi -
>
> I am doing some d
Hi Dave,
I don't think there's a particular limit to it. For a single application,
the idea is to share a single Pulsar client instance.
That makes sure to reuse a lot of resources (threads, TCP connections,
etc..)
For each producer, the biggest amount of memory would be related to the
queue of o
Hi -
I am doing some design work for a message based workflow service I am thinking
about building.
What is the limit on the number of simultaneously open topic producers on a
client node?
Regards,
Dave
signature.asc
Description: Message signed with OpenPGP
