Skip to content
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

Memory and cpu increases when server goes down (socket close) #66

Open
bsocius opened this issue Sep 14, 2015 · 2 comments
Open

Memory and cpu increases when server goes down (socket close) #66

bsocius opened this issue Sep 14, 2015 · 2 comments

Comments

@bsocius
Copy link

bsocius commented Sep 14, 2015

I have noticed a problem in my code or with the node-ddp-client package. When i have have a node-ddp-client connected to the server, and the server for whatever reason goes down, the cpu usages and the memory of the node script goes up.

Is there anything i could do to change this behavior?

Note: This behavior occurs also when the only thing the script does is to make a connection to the server. and no other code is running

Greetings,

Etienne

@emgee3
Copy link
Member

emgee3 commented Sep 14, 2015

Are you saying there is a memory leak, or just that connecting is more resource intensive that listening?

@bsocius
Copy link
Author

bsocius commented Sep 14, 2015

Well i dont know if its a memory leak. I'am not qualified enough to determin this. But maybe somebody could reproduce it, by just creating a node-ddp connection. Then when te connection is established. Stop the Meteor server, and see if memory consumption of the ddp-client is increasing. Let it just run for 10, 15 minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants