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

How to track the change in memory footprint when we change Memory threshold? #65

Open
arunsingh opened this issue Aug 31, 2016 · 0 comments

Comments

@arunsingh
Copy link

How can we check that unicorn worker process are getting killed and process can respawn themselves as per the pre-memory limit set in unicorn/worker_killer module.

What is the memory maths around which we should calculate and set the threshold value of max and min memory limit.

I am not able to read the memory process usage. below is the terminal spit and few things I tried to understand the implementation and observation at the memory level that unicorn/worker_killer is doing its task.

https://gist.github.com/arunsingh/55ad56a45ddbc4e9ee35bfb2896f1ef8

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

1 participant