Node memory usage
I'm running an app that uses a clustering server for serving requests, and I'm having a difficult time figuring out why its memory usage is so high. When each worker process starts, they use around 80MB of memory (the master, in fact, stays at around this level) and over time they balloon to between 225MB and 250MB (measured RSS).
Originally, I thought I had a serious memory leak as this was happening, but the usage definitely levels off at a certain point, so I'm not sure that's the case. I'm also regularly capturing the process.memoryUsage() on these processes—the heap total is 75-100MB, and the heap used is 35-60MB.
On top of this, even when the processes are only using around 100MB (before they've grown to what appears to be their max at 250MB), the total RSS of the server will sit around 1-1.5GB, even though there are no other processes running. This 1-1.5GB metric stays exactly the same, even as the Node workers balloon to 250MB.
Is it possible that Node is doing something that's causing it to take up massive RSS, even beyond what it reports on a per-process basis from process.memoryUsage?
node.js
asked Jun 12 '14 at 14:10
clem
2,74112037
add a comment |
I'm running an app that uses a clustering server for serving requests, and I'm having a difficult time figuring out why its memory usage is so high. When each worker process starts, they use around 80MB of memory (the master, in fact, stays at around this level) and over time they balloon to between 225MB and 250MB (measured RSS).
Originally, I thought I had a serious memory leak as this was happening, but the usage definitely levels off at a certain point, so I'm not sure that's the case. I'm also regularly capturing the process.memoryUsage() on these processes—the heap total is 75-100MB, and the heap used is 35-60MB.
On top of this, even when the processes are only using around 100MB (before they've grown to what appears to be their max at 250MB), the total RSS of the server will sit around 1-1.5GB, even though there are no other processes running. This 1-1.5GB metric stays exactly the same, even as the Node workers balloon to 250MB.
Is it possible that Node is doing something that's causing it to take up massive RSS, even beyond what it reports on a per-process basis from process.memoryUsage?
node.js
asked Jun 12 '14 at 14:10
clem
2,74112037
add a comment |
I'm running an app that uses a clustering server for serving requests, and I'm having a difficult time figuring out why its memory usage is so high. When each worker process starts, they use around 80MB of memory (the master, in fact, stays at around this level) and over time they balloon to between 225MB and 250MB (measured RSS).
Originally, I thought I had a serious memory leak as this was happening, but the usage definitely levels off at a certain point, so I'm not sure that's the case. I'm also regularly capturing the process.memoryUsage() on these processes—the heap total is 75-100MB, and the heap used is 35-60MB.
On top of this, even when the processes are only using around 100MB (before they've grown to what appears to be their max at 250MB), the total RSS of the server will sit around 1-1.5GB, even though there are no other processes running. This 1-1.5GB metric stays exactly the same, even as the Node workers balloon to 250MB.
Is it possible that Node is doing something that's causing it to take up massive RSS, even beyond what it reports on a per-process basis from process.memoryUsage?
node.js
asked Jun 12 '14 at 14:10
clem
2,74112037
I'm running an app that uses a clustering server for serving requests, and I'm having a difficult time figuring out why its memory usage is so high. When each worker process starts, they use around 80MB of memory (the master, in fact, stays at around this level) and over time they balloon to between 225MB and 250MB (measured RSS).
Originally, I thought I had a serious memory leak as this was happening, but the usage definitely levels off at a certain point, so I'm not sure that's the case. I'm also regularly capturing the process.memoryUsage() on these processes—the heap total is 75-100MB, and the heap used is 35-60MB.
On top of this, even when the processes are only using around 100MB (before they've grown to what appears to be their max at 250MB), the total RSS of the server will sit around 1-1.5GB, even though there are no other processes running. This 1-1.5GB metric stays exactly the same, even as the Node workers balloon to 250MB.
Is it possible that Node is doing something that's causing it to take up massive RSS, even beyond what it reports on a per-process basis from process.memoryUsage?
node.js
node.js
asked Jun 12 '14 at 14:10
clem
2,74112037
asked Jun 12 '14 at 14:10
clem
2,74112037
asked Jun 12 '14 at 14:10
clem
2,74112037
asked Jun 12 '14 at 14:10
clem
2,74112037
asked Jun 12 '14 at 14:10
clem
2,74112037
2,74112037
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I have also noticed this exact thing, and also contributed it a memory leak. Wondering if you ever made any progress with this, as I am at a loss to making progress with it.
answered Nov 20 at 19:34
IYE
248
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%2f24186583%2fnode-memory-usage%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
I have also noticed this exact thing, and also contributed it a memory leak. Wondering if you ever made any progress with this, as I am at a loss to making progress with it.
answered Nov 20 at 19:34
IYE
248
add a comment |
I have also noticed this exact thing, and also contributed it a memory leak. Wondering if you ever made any progress with this, as I am at a loss to making progress with it.
answered Nov 20 at 19:34
IYE
248
add a comment |
I have also noticed this exact thing, and also contributed it a memory leak. Wondering if you ever made any progress with this, as I am at a loss to making progress with it.
answered Nov 20 at 19:34
IYE
248
I have also noticed this exact thing, and also contributed it a memory leak. Wondering if you ever made any progress with this, as I am at a loss to making progress with it.
answered Nov 20 at 19:34
IYE
248
answered Nov 20 at 19:34
IYE
248
answered Nov 20 at 19:34
IYE
248
answered Nov 20 at 19:34
IYE
248
248
add a comment |
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%2f24186583%2fnode-memory-usage%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
