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

delayed_job memory leak? #2797

Closed
1c7 opened this issue Dec 9, 2016 · 5 comments
Closed

delayed_job memory leak? #2797

1c7 opened this issue Dec 9, 2016 · 5 comments

Comments

@1c7
Copy link
Contributor

1c7 commented Dec 9, 2016

Sharetribe Version:

6.1.0

Environment:

Ubuntu 14.04

The Problem

After running bundle exec rake jobs:work
This delay job would slowly take up all the memory the server have, and cause server down.
I have to manual restart server at Cloud Provider website (I am using Azure from Microsoft)

How did you guys solve this problem ?

I am thinking about migrate from delayed_job tosidekiq

@rap1ds
Copy link
Member

rap1ds commented Dec 9, 2016

Ping @bladealslayer have you noticed any memory leaks in our production workers?

@bladealslayer
Copy link
Member

No, I haven't, but ours get restarted once per day automatically anyway (by Heroku). @1c7 have you tried setting the ImageMagick-related memory limits? Maybe it's not memory leak, but memory spikes during image processing?

You can try setting these environment variables in the process that starts the workers:

MAGICK_MAP_LIMIT=64MiB
MAGICK_MEMORY_LIMIT=256MiB
MAGICK_TIME_LIMIT=30

@1c7
Copy link
Contributor Author

1c7 commented Dec 10, 2016

@bladealslayer Thank you, I would try your setting.

@1c7
Copy link
Contributor Author

1c7 commented Dec 10, 2016

collectiveidea/delayed_job#823
According to this issue from delayed_job Github repo, I think it's not Image process problem,
But I would try your solution anyway.

Thanks again

I would close this issue in couple day.

once the test result come out.

@1c7
Copy link
Contributor Author

1c7 commented Dec 11, 2016

haven't test. I just decide migrate to sidekiq

@1c7 1c7 closed this as completed Dec 11, 2016
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

3 participants