Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cpu usage gradually increases to 100% #29

Closed
johnfinley opened this issue Mar 18, 2016 · 3 comments
Closed

cpu usage gradually increases to 100% #29

johnfinley opened this issue Mar 18, 2016 · 3 comments

Comments

@johnfinley
Copy link

If our program has an endpoint publishing at a few hundred messages/sec with qos=reliable, the cpu utilization for the process gradually increases until it is consuming all cpu. I modified the example "HelloWorld" program to send messages at a higher rate, and it does it too (although very slowly) when run on an ubuntu-14.04 VM. I have a different test program that can send at higher rates, and the CPU usage runs away pretty quickly. In our "real" program, the message rate is ~100/sec, and it ramps up to 100% within a few minutes (perhaps because of our slower processor). Same effect has been observed on our target hardware, os-x, and linux using our test programs, and has just been confirmed using HelloWorld on an ubuntu-14.04 vm. The HelloWorld test was done in a fresh clone and build on 3/16.

I can add our test programs if helpful, but I figured using HelloWorld would be more useful to you.

Two files attached:

soak-diff.txt is diffs from HelloWorld.

soak-top.txt is output from top on the vm as the pub and sub run on the same vm. I think I used "top -b | grep " where is that of the publisher, so the samples are about 3 seconds apart.

@JaimeMartin
Copy link
Member

Hi John,

We reproduced the issue and identified where is the problem. We will prepare a patch for you.

@JaimeMartin
Copy link
Member

Hi John,

We uploaded a new temp branch(https://github.com/eProsima/Fast-RTPS/tree/hotfix/29) with a fix for your issue. We are testing now everything. Let me know is this solves your problem.

@johnfinley
Copy link
Author

Thanks! We'll be trying it out over the next few days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants