dlg99 commented on issue #9562: URL: https://github.com/apache/pulsar/issues/9562#issuecomment-789119252
another thing to look at is "because of bookie disk latencies" Large messages are a part of the problem (unless you have pulsar chunk them). you need really carefully review bookie configuration to tune it better for the large messages: https://github.com/apache/bookkeeper/blob/master/conf/bk_server.conf At least: ``` byteBufAllocatorSize... nettyMaxFrameSizeBytes journalPreAllocSizeMB journalWriteBufferSizeKB journalBufferedWritesThreshold skipList... readBufferSizeBytes writeBufferSizeBytes ``` probably something else. Can you move journal to a dedicated fast disk? Increase skip list size, especially if you have tailing reads check linux config for the disks, i.e. read-ahead, scheduler for ssds etc., though it feels like a rotational disks ("publishing to a single topic about 150 mb/s"). I had clients writing to bookies being bottlenecked by 20gbps NIC though entries were smaller (~64K) Consider increasing ensemble size for the ledger, this will spread IO across more bookies. i.e. if you running with ES/Wq/Aq of 3/3/2 increase ES to 7, 11 or more. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
