https://pulsar.apache.org/ logo
Join Slack
Powered by
# reactive-pulsar
  • s

    Slackbot

    09/26/2022, 2:09 PM
    This message was deleted.
  • s

    Slackbot

    09/26/2022, 3:23 PM
    This message was deleted.
  • s

    Slackbot

    10/11/2022, 5:01 PM
    This message was deleted.
  • s

    Slackbot

    10/17/2022, 10:45 AM
    This message was deleted.
  • s

    Slackbot

    10/19/2022, 4:50 AM
    This message was deleted.
  • s

    Slackbot

    02/14/2023, 8:42 AM
    This message was deleted.
    a
    l
    +2
    • 5
    • 8
  • s

    Slackbot

    06/14/2023, 8:48 AM
    This message was deleted.
    c
    h
    s
    • 4
    • 12
  • s

    sagar

    07/17/2025, 11:30 AM
    context • ordering required • have partitioning for throughput • using pulsar client (non-reactive) • listener threads are getting shared across internal queue in a blocking fashion • mostly io ques: in order to have higher throughput i can increase listener threads so that internal queues processing do not block each others. partitions and topics will increase and therefore there’s not end to it. How can pulsar reactive client help with this? i want high throughput with less number of thread. how does it overcome native pulsar client listeners blocking behaviour? pipelining i am aware of but it seems conflicting with partitions
    l
    • 2
    • 1