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

Open
mvysny opened this Issue Dec 7, 2016 · 10 comments

Comments

Projects
None yet
6 participants
@mvysny

mvysny commented Dec 7, 2016

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.
screenshot from 2016-12-07 10-09-26

@mvysny mvysny changed the title from Couchbase community 4.5.0 erlang eating CPU to Couchbase community 4.5.0 erlang/beam.smp eating CPU Dec 7, 2016

@makedir

This comment has been minimized.

makedir commented Feb 26, 2017

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.

@serragnoli

This comment has been minimized.

serragnoli commented Aug 16, 2017

Hi @makedir.
Did you get to the bottom of this issue?

@makedir

This comment has been minimized.

makedir commented Aug 16, 2017

Nope. Erlang still draining CPU of about 2-3% permanently, even on a brand new Ubuntu Server installation.

@hubyhuby

This comment has been minimized.

hubyhuby commented Aug 23, 2017

Exact same behaviour on my Ubuntu 17.04. 64 bits and Couchbase 4.5.1 // CPU i5 HQ
I have the sample databases with a full text search index; sitting IDLE and it takes 20-30% of the CPU all the time. (I noticed because I am running the server on my laptop and it gets hotter)
I am evaluating aswell, but am wondering if an empty database with no request placed, takes 30% of a moderne CPU....what would it be with 10 requests ;)

I think at the very first start the behaviour was normal, within 2-3%

@hubyhuby

This comment has been minimized.

hubyhuby commented Aug 26, 2017

couchbugcpuidle
PS: @makedir , 2-3% is something normal. ElasticSearch is also at 3% IDLE. But 30% IDLE is not something habitual. If I have 3 processes like this on my server, I can shut it down.

@makedir

This comment has been minimized.

makedir commented Aug 27, 2017

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.

@xiaoyaozi5566

This comment has been minimized.

xiaoyaozi5566 commented Jan 24, 2018

I saw the same issue. beam.smp eating up tons of CPU. Can anyone help?

@hubyhuby

This comment has been minimized.

hubyhuby commented Jan 25, 2018

Dear @xiaoyaozi5566,
I came to the conclusion that if you want the real thing without the bug you have to go with the pro version... They don t seem to give much love to the free version unfortunately... They don t do much updates on thise one

@grreeenn

This comment has been minimized.

grreeenn commented Apr 15, 2018

Same here.
Clean CE 5.0 installation wit one EMPTY bucket. No data, no connections to DB, just a clean test installation on my laptop.
Here's the screenshot from the Couchbase UI itself
cb_cpu_idle

Any update?

@grreeenn

This comment has been minimized.

grreeenn commented Apr 15, 2018

OK, found this on Couchbase JIRA; see Dave's comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment