This repository was archived by the owner on Apr 23, 2025. It is now read-only.
Open
Conversation
Member
|
super interested to hear how this goes @waysidekoi |
Contributor
Author
|
me too :) |
Contributor
Author
|
has platform tried it? |
Member
|
we haven't. we're currently using monit to restart sidekiq processes when they get too big. |
Contributor
Author
|
So far so great: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR opts to build a docker image for Ruby 2.3.1 using the
jemalloclibrary as suggested here: https://www.levups.com/en/blog/2017/optimize_ruby_memory_usage_jemalloc_heroku_scalingo.html.The PRS application noticed that Sidekiq was eating an uncontrollable amount of memory. In an attempt to address this, try a different library for memory allocation