ckdarby commented on issue #7058: URL: https://github.com/apache/pulsar/issues/7058#issuecomment-635081278
@ashwallace Thanks for everything. I'll nuke the cluster & change the type with a baseline higher and let you know. Here are my other comments... >In your graphs, bookie is also exceeding the baseline (bursting) often too (150MBs peak observed). That view you're referencing is the bookie overview view, it includes all four bookies. What it looks like just on specifically "public/cory/test-ebs-partition-5" topic only which is where the pulsar perf reader was against, can be seen [here](https://user-images.githubusercontent.com/220283/83075150-5f469100-a041-11ea-9ee7-b078fb65b99d.png). Much less than 150 MB/s :(. >Generally, no application will attain the performance that a benchmarking tool would Of course, but I was hoping for even half which would be closer to ~100 MB/s >Interestingly enough, the pulsar documentation itself recommends i3 instance types which have their own NVMe disks This is the non-kubernetes bare metal way. Kubernetes if you're using AWS's managed version called EKS has a default pvc of EBS gp2. With Kubernetes typically I try to avoid specialised nodes like the i3 type because then you need to limit what pods are going on them because you only want pods that will leverage the NVME SSDs. ---------------------------------------------------------------- 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
