ckdarby commented on issue #7058: URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635684753
@ashwallace Upgrade to c5.4xlarge ```text 23:47:19.989 [main] INFO org.apache.pulsar.testclient.PerformanceReader - Read throughput: 59245.241 msg/s -- 678.398 Mbit/s 23:47:29.989 [main] INFO org.apache.pulsar.testclient.PerformanceReader - Read throughput: 56308.718 msg/s -- 648.628 Mbit/s 23:47:39.996 [main] INFO org.apache.pulsar.testclient.PerformanceReader - Read throughput: 52245.146 msg/s -- 593.771 Mbit/s 23:47:49.996 [main] INFO org.apache.pulsar.testclient.PerformanceReader - Read throughput: 59516.311 msg/s -- 657.495 Mbit/s 23:47:59.996 [main] INFO org.apache.pulsar.testclient.PerformanceReader - Read throughput: 49080.654 msg/s -- 538.890 Mbit/s 23:48:09.996 [main] INFO org.apache.pulsar.testclient.PerformanceReader - Read throughput: 61823.387 msg/s -- 683.237 Mbit/s ``` Still seeing the same kind of issue, tomorrow I can rerun the test and repost all the graphs. @sijie I'm thinking this pretty much rules out EBS/AWS as an issue. I saw the same thing even when I took Ash's advice to get better EBS baseline throughput. The per ops tend to be on average 150 KiB. Is there any specific params on bookie that determines how much it reads off the ledger into the read cache at a time? This mostly now just looks like a bookie tuning thing with prefetch when the cache is missed on backlog and it isn't being very aggressive. Let me know or pull in someone if there is someone better suited on the Pulsar side. ---------------------------------------------------------------- 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: us...@infra.apache.org
