You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/09/14 16:10:21 UTC

[GitHub] [pulsar] lhotari commented on pull request #12037: [Client] Support passing existing executor providers to the client

lhotari commented on pull request #12037:
URL: https://github.com/apache/pulsar/pull/12037#issuecomment-919298722


   > Do you want to use this only inside internal Pulsar tools ? the Proxy, Pulsar perf, Pulsar CLI tools ?
   
   yes, mainly an internal, unsupported API. Pulsar Proxy and Pulsar perf are the main internal use cases.
   
   > Why can't we add this support using the regular PulsarClient Builder API ?
   
   It seems that this would just add unnecessary complexity and extra baggage in the public API. 
   I'd assume that there are very few use cases where there would be a need to specify the thread pools to use.
   
   My use case is in improving [nosqlbench's Pulsar driver](https://github.com/nosqlbench/nosqlbench/tree/main/driver-pulsar). This would allow to emulate thousands of isolated Pulsar clients within a single JVM. When a Pulsar client is shared, it doesn't properly emulate real production work loads.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org