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

Child process memory keeps growing #136

Closed
phuongnd08 opened this issue Oct 10, 2015 · 2 comments
Closed

Child process memory keeps growing #136

phuongnd08 opened this issue Oct 10, 2015 · 2 comments

Comments

@phuongnd08
Copy link

I was observing the behavior of resque-pool on a Mac.
We have resque pool forking 5 child processes doing nothing.
Right after successful forking, the parent resque-pool process took 120M and each child resque process took less than 20M. But after 5 minutes, memory start growing up to 110M per child resque process even though they were not doing anything. This led to aggressive memory usage in Heroku causing memory to keep getting swapped out to disk. Could you recommend a solution? I'm looking for a way to figure out the reason why idle child process keeps eating memory as well as a way to kill and refork them if memory has been grown too much.

@clintmod
Copy link

@phuongnd08 did you solve this? I'm seeing the same thing.

@phuongnd08
Copy link
Author

What I did is to use dynamic loader to periodically kill the child process to prevent that.

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