Hi, We already have a default number of threads for persistent topics but we have added a feature non-persistent topics and to isolate that path we introduced a number of worker threads which we can reduce or tune based on resources we would like to allocate for non-persistent topics. So, it really doesn't make sense and I don't see any clear reason in this PIP why we would like to take away control to tune thread resources to non-persistent topics.
Thanks, Rajan On Mon, Jun 5, 2023 at 10:56 PM houxiaoyu <anonhx...@gmail.com> wrote: > Hi Pulsar Community, > > I am writing to start the discussion on PIP-275: Introduce > numWorkerThreadsForPersistentTopic to deprecate > numWorkerThreadsForNonPersistentTopic in configuration > > PR with PIP contents: https://github.com/apache/pulsar/pull/20507 > > # Motivation > > Introduce `numWorkerThreadsForPersistentTopic` to deprecate > `numWorkerThreadsForNonPersistentTopic`. > > The `numWorkerThreadsForNonPersistentTopic` is used to specify for > PersistentTopic, not NonPersistentTopic. So I propose change the config > item from `numWorkerThreadsForNonPersistentTopic` to > `numWorkerThreadsForPersistentTopic`: > > Thanks, > Xiaoyu Hou >
