Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Java client: high CPU regression for producer between 2.6.x and 2.7.x

See original GitHub issue

Describe the bug When upgrading our pulsar client to 2.7.x, we noticed significantly higher CPU used for applications running multiple produces with the newer version. We have been unable to isolate the exact cause of the regression.

To Reproduce Steps to reproduce the behavior:

Run the example dropwizard application at https://github.com/klevy-toast/dropwizard-pulsar-test/
Run ./while.sh to trigger continuous message production
Observe average CPU over time
Change pulsar version in pom.xml, repeat 1-3

Expected behavior CPU usage should be fairly similar between versions. But something in 2.7.x is clearly using more resources.

Screenshots I tested this by running the application on an AWS t3a.large EC2 instance – there was a ~15% increase in CPU.

Desktop (please complete the following information):

OS: linux

Issue Analytics

State:
Created 2 years ago
Comments:11 (7 by maintainers)

Top GitHub Comments

1reaction

eolivellicommented, Jan 7, 2022

Can you test your suggestion on current master branch? If you get good results please send a PR

0reactions

michaeljmarshallcommented, Feb 9, 2022

I think that https://github.com/apache/pulsar/pull/14185 might prove to be an even more optimal solution, especially when running with many producers that are not in user. I haven’t completed any bench marks yet, though.