[GitHub] [pulsar] eolivelli commented on issue #14233: [Performance Tuning] The performance improvement of Apache pulsar has encountered a bottleneck. No matter how to modify the configuration parameters, the performance can not be effectively improved

[GitBox <gi...@apache.org>]

eolivelli commented on issue #14233:
URL: https://github.com/apache/pulsar/issues/14233#issuecomment-1035968350


   hello, if you want to do performance testing I suggest you to:
   - install the component on separate machines
   - for write workloads the bottleneck is usually the disk of the Journal on the bookie, ensure to have a good disk
   - usually it is better to enlarge the writeCache on the Bookie in conf/bookkeeper.conf:
   ```
     dbStorage_rocksDB_blockCacheSize: '4294967296'
     dbStorage_writeCacheMaxSizeMb: '2048'
   ```
   - you can use partitioned topics in order to spread the load among several brokers, and also even with a single broker with partitioned topics you can use better the resources of the broker
   
   


-- 
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