Is this a memory leak or a high-memory use JS app?
I'm trying to figure out some performance issues that our node.js app is having. We're on 8.11.1. I haven't dived into heap dumps yet, that's the next step but before I do, I thought I'd seek out another opinion or two. I spun up productions servers at the moments where that line is vertical and since then, it seems like multiple instances are constantly running at about ~60% memory utilization.
If this is not in fact a memory leak, what are some things that we can do to get overall memory utilization down to a lower level?
Thanks!
javascript node.js amazon-web-services amazon-ec2 amazon-cloudwatch
add a comment |
I'm trying to figure out some performance issues that our node.js app is having. We're on 8.11.1. I haven't dived into heap dumps yet, that's the next step but before I do, I thought I'd seek out another opinion or two. I spun up productions servers at the moments where that line is vertical and since then, it seems like multiple instances are constantly running at about ~60% memory utilization.
If this is not in fact a memory leak, what are some things that we can do to get overall memory utilization down to a lower level?
Thanks!
javascript node.js amazon-web-services amazon-ec2 amazon-cloudwatch
Have you tried node-clinic-docktor ? It helps to figure out your performance issues
– lependu
Nov 13 '18 at 18:25
I haven't. Will look into now.
– Zack Shapiro
Nov 13 '18 at 18:35
add a comment |
I'm trying to figure out some performance issues that our node.js app is having. We're on 8.11.1. I haven't dived into heap dumps yet, that's the next step but before I do, I thought I'd seek out another opinion or two. I spun up productions servers at the moments where that line is vertical and since then, it seems like multiple instances are constantly running at about ~60% memory utilization.
If this is not in fact a memory leak, what are some things that we can do to get overall memory utilization down to a lower level?
Thanks!
javascript node.js amazon-web-services amazon-ec2 amazon-cloudwatch
I'm trying to figure out some performance issues that our node.js app is having. We're on 8.11.1. I haven't dived into heap dumps yet, that's the next step but before I do, I thought I'd seek out another opinion or two. I spun up productions servers at the moments where that line is vertical and since then, it seems like multiple instances are constantly running at about ~60% memory utilization.
If this is not in fact a memory leak, what are some things that we can do to get overall memory utilization down to a lower level?
Thanks!
javascript node.js amazon-web-services amazon-ec2 amazon-cloudwatch
javascript node.js amazon-web-services amazon-ec2 amazon-cloudwatch
asked Nov 13 '18 at 18:20
Zack ShapiroZack Shapiro
1,08284083
1,08284083
Have you tried node-clinic-docktor ? It helps to figure out your performance issues
– lependu
Nov 13 '18 at 18:25
I haven't. Will look into now.
– Zack Shapiro
Nov 13 '18 at 18:35
add a comment |
Have you tried node-clinic-docktor ? It helps to figure out your performance issues
– lependu
Nov 13 '18 at 18:25
I haven't. Will look into now.
– Zack Shapiro
Nov 13 '18 at 18:35
Have you tried node-clinic-docktor ? It helps to figure out your performance issues
– lependu
Nov 13 '18 at 18:25
Have you tried node-clinic-docktor ? It helps to figure out your performance issues
– lependu
Nov 13 '18 at 18:25
I haven't. Will look into now.
– Zack Shapiro
Nov 13 '18 at 18:35
I haven't. Will look into now.
– Zack Shapiro
Nov 13 '18 at 18:35
add a comment |
0
active
oldest
votes
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%2f53287274%2fis-this-a-memory-leak-or-a-high-memory-use-js-app%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f53287274%2fis-this-a-memory-leak-or-a-high-memory-use-js-app%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
Have you tried node-clinic-docktor ? It helps to figure out your performance issues
– lependu
Nov 13 '18 at 18:25
I haven't. Will look into now.
– Zack Shapiro
Nov 13 '18 at 18:35