Couchbase internal processes taking a lot of CPU
I am using couchbase 5.0.1
Couchbase internal processes like beam.smp, indexer and cbq-engine are taking a lot of CPU.
Can you please tell me how to tune these processes so that they take less CPU?
couchbase couchbase-java-api asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
add a comment |
I am using couchbase 5.0.1
Couchbase internal processes like beam.smp, indexer and cbq-engine are taking a lot of CPU.
Can you please tell me how to tune these processes so that they take less CPU?
couchbase couchbase-java-api asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
1
What's happening while this is going on? Is the database warmed up and idle?
– Hod
Nov 12 '18 at 16:26
1
Issue is that we are reaching end of resources with just 2 concurrent users. This should not happen. Not sure whether DB is warmed up or idle.
– Bhuvan
Nov 13 '18 at 10:39
add a comment |
I am using couchbase 5.0.1
Couchbase internal processes like beam.smp, indexer and cbq-engine are taking a lot of CPU.
Can you please tell me how to tune these processes so that they take less CPU?
couchbase couchbase-java-api asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
I am using couchbase 5.0.1
Couchbase internal processes like beam.smp, indexer and cbq-engine are taking a lot of CPU.
Can you please tell me how to tune these processes so that they take less CPU?
couchbase couchbase-java-api couchbase couchbase-java-api asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
asked Nov 12 '18 at 13:58
Bhuvan
1,25972340
1,25972340
1
What's happening while this is going on? Is the database warmed up and idle?
– Hod
Nov 12 '18 at 16:26
1
Issue is that we are reaching end of resources with just 2 concurrent users. This should not happen. Not sure whether DB is warmed up or idle.
– Bhuvan
Nov 13 '18 at 10:39
add a comment |
1
What's happening while this is going on? Is the database warmed up and idle?
– Hod
Nov 12 '18 at 16:26
1
Issue is that we are reaching end of resources with just 2 concurrent users. This should not happen. Not sure whether DB is warmed up or idle.
– Bhuvan
Nov 13 '18 at 10:39
1
1
What's happening while this is going on? Is the database warmed up and idle?
– Hod
Nov 12 '18 at 16:26
What's happening while this is going on? Is the database warmed up and idle?
– Hod
Nov 12 '18 at 16:26
1
1
Issue is that we are reaching end of resources with just 2 concurrent users. This should not happen. Not sure whether DB is warmed up or idle.
– Bhuvan
Nov 13 '18 at 10:39
Issue is that we are reaching end of resources with just 2 concurrent users. This should not happen. Not sure whether DB is warmed up or idle.
– Bhuvan
Nov 13 '18 at 10:39
add a comment |
1 Answer
1
active
oldest
votes
To get the load on the query engine (cbq-engine) down, you need to find out what is causing the load. This article has a lot of information about query profiling:
https://blog.couchbase.com/optimize-n1ql-performance-using-request-profiling/
answered Nov 13 '18 at 11:50
Johan Larson
794511
1
Hi Johan, after upgrading to Couchbase 5.5, CPU usage for both cbq-engine and indexer is now down. But it is still high (or 10% improvement) in beam.smp
– Bhuvan
Nov 13 '18 at 17:02
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263727%2fcouchbase-internal-processes-taking-a-lot-of-cpu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
To get the load on the query engine (cbq-engine) down, you need to find out what is causing the load. This article has a lot of information about query profiling:
https://blog.couchbase.com/optimize-n1ql-performance-using-request-profiling/
answered Nov 13 '18 at 11:50
Johan Larson
794511
1
Hi Johan, after upgrading to Couchbase 5.5, CPU usage for both cbq-engine and indexer is now down. But it is still high (or 10% improvement) in beam.smp
– Bhuvan
Nov 13 '18 at 17:02
add a comment |
To get the load on the query engine (cbq-engine) down, you need to find out what is causing the load. This article has a lot of information about query profiling:
https://blog.couchbase.com/optimize-n1ql-performance-using-request-profiling/
answered Nov 13 '18 at 11:50
Johan Larson
794511
1
Hi Johan, after upgrading to Couchbase 5.5, CPU usage for both cbq-engine and indexer is now down. But it is still high (or 10% improvement) in beam.smp
– Bhuvan
Nov 13 '18 at 17:02
add a comment |
To get the load on the query engine (cbq-engine) down, you need to find out what is causing the load. This article has a lot of information about query profiling:
https://blog.couchbase.com/optimize-n1ql-performance-using-request-profiling/
answered Nov 13 '18 at 11:50
Johan Larson
794511
To get the load on the query engine (cbq-engine) down, you need to find out what is causing the load. This article has a lot of information about query profiling:
https://blog.couchbase.com/optimize-n1ql-performance-using-request-profiling/
answered Nov 13 '18 at 11:50
Johan Larson
794511
answered Nov 13 '18 at 11:50
Johan Larson
794511
answered Nov 13 '18 at 11:50
Johan Larson
794511
answered Nov 13 '18 at 11:50
Johan Larson
794511
794511
1
Hi Johan, after upgrading to Couchbase 5.5, CPU usage for both cbq-engine and indexer is now down. But it is still high (or 10% improvement) in beam.smp
– Bhuvan
Nov 13 '18 at 17:02
add a comment |
1
Hi Johan, after upgrading to Couchbase 5.5, CPU usage for both cbq-engine and indexer is now down. But it is still high (or 10% improvement) in beam.smp
– Bhuvan
Nov 13 '18 at 17:02
1
1
Hi Johan, after upgrading to Couchbase 5.5, CPU usage for both cbq-engine and indexer is now down. But it is still high (or 10% improvement) in beam.smp
– Bhuvan
Nov 13 '18 at 17:02
Hi Johan, after upgrading to Couchbase 5.5, CPU usage for both cbq-engine and indexer is now down. But it is still high (or 10% improvement) in beam.smp
– Bhuvan
Nov 13 '18 at 17:02
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263727%2fcouchbase-internal-processes-taking-a-lot-of-cpu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
What's happening while this is going on? Is the database warmed up and idle?
– Hod
Nov 12 '18 at 16:26
1
Issue is that we are reaching end of resources with just 2 concurrent users. This should not happen. Not sure whether DB is warmed up or idle.
– Bhuvan
Nov 13 '18 at 10:39