-
Notifications
You must be signed in to change notification settings - Fork 12
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
Couchbase community 4.5.0 erlang/beam.smp eating CPU #4
Comments
I see the same behavior: http://i.imgur.com/pJ3eOK9.png What is this? Permanent 2 x 3% idle on a xeon 4core is a lot, what is causing this? There are no connections on the couchdb right now. |
Hi @makedir. |
Nope. Erlang still draining CPU of about 2-3% permanently, even on a brand new Ubuntu Server installation. |
Exact same behaviour on my Ubuntu 17.04. 64 bits and Couchbase 4.5.1 // CPU i5 HQ I think at the very first start the behaviour was normal, within 2-3% |
|
No... that's not NORMAL @hubyhuby Normal is, when idle takes 0% CPU. I will just remove this damn piece of a crap software I guess. It mostly wont ever get fixed. I see this bug back in reports going back now 5years or longer. |
I saw the same issue. beam.smp eating up tons of CPU. Can anyone help? |
Dear @xiaoyaozi5566, |
OK, found this on Couchbase JIRA; see Dave's comment. |
I am running a docker version of Couchbase community, as follows:
docker run --rm -ti --net=couchbase --name couchbase-server -p 127.0.0.1:8091-8094:8091-8094 -p 127.0.0.1:11210:11210 couchbase/server:community-4.5.0
The host OS is a 64-bit Ubuntu 16.10. The server has been configured with default values. There are two buckets, default (which is completely empty) and the beer sample database. The erlang process is constantly eating ~30% of one CPU core even though the Couchbase server has been sitting idle with no inbound requests for at least an hour (this is just a testing instance so I'm pretty sure it does nothing).
Attaching a screenshot of htop confirming the issue.
The text was updated successfully, but these errors were encountered: