-
Notifications
You must be signed in to change notification settings - Fork 109
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
CPU usage 100%, app frozen #42
Comments
Is that only with past couple of hours? If possible, we can schedule a Dtrace profiling session for your app. So we might can findout the issue. |
I've just re-enabled Kadira and used the app with only one user. CPU got to 100% in 4 minutes. The console says The problem has been happening only for the past hour actually, since around 21:30 Pacific. There have been changes in user access patterns before 21:30 today, because we launched officially, but right now it's past market hours so there are no users on the site. Unfortunately we need to keep this production instance up so I'll be disabling Kadira for the moment. |
Okay. It seems fair to remove kadira. |
What's the node version you are running? I kind a see high CPU usage under node 0.10.30 on Telescope. But didn't check after removing Kadira. |
I can confirm this is with node version |
Standard Meteor 0.8.3, node v0.10.30. Kadira also caused a ~4x memory leak (150MB -> ~600-700MB app size in RAM) in our backend app, which has no clients connecting to the server. That app does a lot of Mongo inserts. |
Thanks dan. We are on the way to fix it. Let's see. On Wednesday, August 6, 2014, Dan Dascalescu notifications@github.com
Arunoda Susiripala @arunoda http://twitter.com/arunoda |
dtrace shows it as a timers issue. So here's the bug: nodejs/node-v0.x-archive#8065 I'll try to give it a fix anyway from our side. |
Awesome, thanks for the work! Looking forward to re-enable Kadira. |
node 0.10.30 introduced a bug which caused 100% CPU usage if do a timeout with a non integer value. see: #8065 And it causes #42 This will fix that issue on kadira
Dan, update kadira and I've done a fix. Can you please check. Note:
|
This bug is not anymore and only node version 0.10.29 had this issue. |
It looks like within the past few hours, Kadira has been blocking our app.
htop
showed 100% or more CPU usage, and http://stockbase.com:3000 would never complete loading.After removing
kadira
from.meteor/packages
and theKadira.connect(Meteor.settings.Kadira.appId, Meteor.settings.Kadira.appSecret);
server code, the app runs normally (<5% CPU usage).What made me suspect Kadira was the culprit is that I saw the
Kadira: successfully authenticated
message, but not theKadira: completed instrumenting the app
one despite waiting for ~15 minutes.The text was updated successfully, but these errors were encountered: