I don't have any experience with Sidekiq so hopefully someone else on the team will chime in but from a quick search it seems like this is a known issue. You mentioned you have tried numerous things you have seen online so if you have seen these already feel free to ignore:
Thanks Christina! I'd actually found that and forgot to mention I implemented it.
After a bit more research I found it interesting how Sidekiq/Ruby handles memory (I'm a RoR newb). I noticed when Sidekiq finished a job that the memory did not get released back to the OS. And I subsequently learned that it just releases it back to Ruby. The process then just slowly increments its memory over time and blows the gasket on my dynos unless I kill them.
I've ended up implementing github.com/klaxit/sidekiq-worker-k... and it's working great! I haven't noticed any side effects, but my community is in its infant stages right now so I'm keeping a close eye on it.
For further actions, you may consider blocking this person and/or reporting abuse
I don't have any experience with Sidekiq so hopefully someone else on the team will chime in but from a quick search it seems like this is a known issue. You mentioned you have tried numerous things you have seen online so if you have seen these already feel free to ignore:
Reducing Sidekiq memory useage with jamalloc
And the issue where they found that 👆 info
Thanks Christina! I'd actually found that and forgot to mention I implemented it.
After a bit more research I found it interesting how Sidekiq/Ruby handles memory (I'm a RoR newb). I noticed when Sidekiq finished a job that the memory did not get released back to the OS. And I subsequently learned that it just releases it back to Ruby. The process then just slowly increments its memory over time and blows the gasket on my dynos unless I kill them.
I've ended up implementing github.com/klaxit/sidekiq-worker-k... and it's working great! I haven't noticed any side effects, but my community is in its infant stages right now so I'm keeping a close eye on it.